From: Greg KH <gregkh@linuxfoundation.org>
To: Antoine Tenart <atenart@kernel.org>
Cc: stable@vger.kernel.org, Willem de Bruijn <willemb@google.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH 5.15.y] gro: fix ownership transfer
Date: Mon, 8 Apr 2024 13:28:41 +0200 [thread overview]
Message-ID: <2024040831-broker-sandfish-a30d@gregkh> (raw)
In-Reply-To: <20240408094416.68848-1-atenart@kernel.org>
On Mon, Apr 08, 2024 at 11:44:16AM +0200, Antoine Tenart wrote:
> commit ed4cccef64c1d0d5b91e69f7a8a6697c3a865486 upstream.
>
> 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>
> Signed-off-by: David S. Miller <davem@davemloft.net>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-04-08 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 10:17 FAILED: patch "[PATCH] gro: fix ownership transfer" failed to apply to 5.15-stable tree gregkh
2024-04-08 9:44 ` [PATCH 5.15.y] gro: fix ownership transfer Antoine Tenart
2024-04-08 11:28 ` Greg KH [this message]
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=2024040831-broker-sandfish-a30d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=stable@vger.kernel.org \
--cc=willemb@google.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