netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Antoine Tenart <atenart@kernel.org>,
	 davem@davemloft.net,  kuba@kernel.org,  pabeni@redhat.com,
	 edumazet@google.com
Cc: Antoine Tenart <atenart@kernel.org>,
	 steffen.klassert@secunet.com,  willemdebruijn.kernel@gmail.com,
	 netdev@vger.kernel.org
Subject: Re: [PATCH net v2 2/4] gro: fix ownership transfer
Date: Tue, 19 Mar 2024 09:13:19 -0400	[thread overview]
Message-ID: <65f98f6faf355_11543d294d4@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20240319093140.499123-3-atenart@kernel.org>

Antoine Tenart wrote:
> If packets are GROed with fraglist they might be segmented later on and
> continue their journey in the stack. In skb_segment_list those skbs can
> be reused as-is. This is an issue as their destructor was removed in
> skb_gro_receive_list but not the reference to their socket, and then
> they can't be orphaned. Fix this by also removing the reference to the
> socket.
> 
> For example this could be observed,
> 
>   kernel BUG at include/linux/skbuff.h:3131!  (skb_orphan)
>   RIP: 0010:ip6_rcv_core+0x11bc/0x19a0
>   Call Trace:
>    ipv6_list_rcv+0x250/0x3f0
>    __netif_receive_skb_list_core+0x49d/0x8f0
>    netif_receive_skb_list_internal+0x634/0xd40
>    napi_complete_done+0x1d2/0x7d0
>    gro_cell_poll+0x118/0x1f0
> 
> A similar construction is found in skb_gro_receive, apply the same
> change there.
> 
> Fixes: 5e10da5385d2 ("skbuff: allow 'slow_gro' for skb carring sock reference")
> Signed-off-by: Antoine Tenart <atenart@kernel.org>

Reviewed-by: Willem de Bruijn <willemb@google.com>

The BUG_ON in skb_orphan makes the invariant clear that the two fields
must be cleared together:

        if (skb->destructor) {
                skb->destructor(skb);
                skb->destructor = NULL;
                skb->sk         = NULL;
        } else {
                BUG_ON(skb->sk);
        }

  reply	other threads:[~2024-03-19 13:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19  9:31 [PATCH net v2 0/4] gro: various fixes related to UDP tunnels Antoine Tenart
2024-03-19  9:31 ` [PATCH net v2 1/4] udp: do not accept non-tunnel GSO skbs landing in a tunnel Antoine Tenart
2024-03-20  2:41   ` Jakub Kicinski
2024-03-20 11:11     ` Antoine Tenart
2024-03-20 10:34   ` Nikolay Aleksandrov
2024-03-20 11:13     ` Antoine Tenart
2024-03-19  9:31 ` [PATCH net v2 2/4] gro: fix ownership transfer Antoine Tenart
2024-03-19 13:13   ` Willem de Bruijn [this message]
2024-03-19  9:31 ` [PATCH net v2 3/4] udp: do not transition UDP fraglist to unnecessary checksum Antoine Tenart
2024-03-19 13:38   ` Willem de Bruijn
2024-03-19 16:01     ` Antoine Tenart
2024-03-20 13:00       ` Willem de Bruijn
2024-03-20 15:08         ` Antoine Tenart
2024-03-20 20:43           ` Willem de Bruijn
2024-03-21  8:48             ` Antoine Tenart
2024-03-21 12:42               ` Paolo Abeni
2024-03-21 14:58               ` Willem de Bruijn
2024-03-21 17:22                 ` Antoine Tenart
2024-03-21 18:13                   ` Willem de Bruijn
2024-03-22 10:48                     ` Antoine Tenart
2024-03-19  9:31 ` [PATCH net v2 4/4] udp: prevent local UDP tunnel packets from being GROed Antoine Tenart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=65f98f6faf355_11543d294d4@willemb.c.googlers.com.notmuch \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).