Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753522AbdCAXZH (ORCPT ); Wed, 1 Mar 2017 18:25:07 -0500 Received: from mail-it0-f50.google.com ([209.85.214.50]:38605 "EHLO mail-it0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751320AbdCAXZC (ORCPT ); Wed, 1 Mar 2017 18:25:02 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Eric Dumazet Date: Wed, 1 Mar 2017 15:15:54 -0800 Message-ID: Subject: Re: net: use-after-free in neigh_timer_handler/sock_wfree To: Cong Wang Cc: Dmitry Vyukov , David Miller , netdev , LKML , syzkaller , Alexey Kuznetsov , James Morris Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 457 Lines: 14 On Wed, Mar 1, 2017 at 3:09 PM, Cong Wang wrote: > > But I doubt skb_orphan() is the solution here, shouldn't we just > update sk->sk_wmem_alloc with skb->truesize changes? Is it worth it ? Apart from syszkaller I mean... We started with something that had a real impact on real workloads. 158f323b9868b59967ad96957c4ca388161be321 net: adjust skb->truesize in pskb_expand_head() Note that auditing the stack took me a while.