All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine Tenart <atenart@kernel.org>
To: zhaoping.shu@mediatek.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	 pabeni@redhat.com, horms@kernel.org, ncardwell@google.com,
	kuniyu@google.com,  matthias.bgg@gmail.com,
	angelogioacchino.delregno@collabora.com, willemb@google.com,
	 alice@isovalent.com, sd@queasysnail.net,
	eilaimemedsnaimel@gmail.com,  imv4bel@gmail.com,
	hw.he@mediatek.com, netdev@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-mediatek@lists.infradead.org, haijun.liu@mediatek.com,
	xiayu.zhang@mediatek.com,  lambert.wang@mediatek.com
Subject: Re: [PATCH net v1] net: gro: avoid nesting GSO skbs in skb_gro_receive_list()
Date: Wed, 22 Jul 2026 10:17:43 +0200	[thread overview]
Message-ID: <amB7wb1A2Oo2dv5d@kwain> (raw)
In-Reply-To: <20260722024214.24845-1-zhaoping.shu@mediatek.com>

On Wed, Jul 22, 2026 at 10:42:14AM +0800, zhaoping.shu@mediatek.com wrote:
> From: HW He <hw.he@mediatek.com>
> 
> On devices that support both NETIF_F_GRO_HW and NETIF_F_GRO_FRAGLIST,
> the hardware or driver may deliver packets that have already been
> aggregated into a GSO skb, either with frags[] or frag_list. GRO may
> then
> aggregate the skb again in skb_gro_receive_list().
> 
> This can create a nested GSO skb, which is not handled correctly by the
> later GSO segmentation paths. When the skb is segmented by
> skb_segment_list(), it not be fully restored to the original packets.
> 
> If the skb is marked with SKB_GSO_DODGY before segmentation, for example
> after a protocol change from IPv6 to IPv4, the nested GSO skb is
> segmented
> by skb_segment(), which may hit a NULL pointer dereference when the skb
> contains a nested frag_list.
> 
> Avoid this by setting NAPI_GRO_CB(skb)->flush for GSO skbs before
> aggregation and by checking the flush flag in skb_gro_receive_list(),
> following the existing logic in skb_gro_receive().
> 
> Signed-off-by: HW He <hw.he@mediatek.com>
> Signed-off-by: Zhaoping Shu <zhaoping.shu@mediatek.com>
> ---
>  net/core/gro.c         | 2 +-
>  net/ipv4/tcp_offload.c | 1 +
>  2 files changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/net/core/gro.c b/net/core/gro.c
> index 35f2f708f010..27c9813495f3 100644
> --- a/net/core/gro.c
> +++ b/net/core/gro.c
> @@ -229,7 +229,7 @@ int skb_gro_receive(struct sk_buff *p, struct sk_buff *skb)
>  
>  int skb_gro_receive_list(struct sk_buff *p, struct sk_buff *skb)
>  {
> -	if (unlikely(p->len + skb->len >= 65536))
> +	if (unlikely(p->len + skb->len >= 65536 || NAPI_GRO_CB(skb)->flush))
>  		return -E2BIG;

This was already fixed in e751256486d0 ("net: gro: fix double
aggregation of flush-marked skbs").
>  
>  	if (!pskb_may_pull(skb, skb_gro_offset(skb))) {
> diff --git a/net/ipv4/tcp_offload.c b/net/ipv4/tcp_offload.c
> index 3b1fdcd3cb29..c363434a5646 100644
> --- a/net/ipv4/tcp_offload.c
> +++ b/net/ipv4/tcp_offload.c
> @@ -332,6 +332,7 @@ struct sk_buff *tcp_gro_receive(struct list_head *head, struct sk_buff *skb,
>  		flush |= skb->ip_summed != p->ip_summed;
>  		flush |= skb->csum_level != p->csum_level;
>  		flush |= NAPI_GRO_CB(p)->count >= 64;
> +		NAPI_GRO_CB(skb)->flush |= skb_is_gso(skb);
>  		skb_set_network_header(skb, skb_gro_receive_network_offset(skb));
>  
>  		if (flush || skb_gro_receive_list(p, skb))

I haven't looked closely but this looks like a second issue and would
need its own patch with a proper description.

Thanks,
Antoine

      reply	other threads:[~2026-07-22  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  2:42 [PATCH net v1] net: gro: avoid nesting GSO skbs in skb_gro_receive_list() zhaoping.shu
2026-07-22  8:17 ` Antoine Tenart [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=amB7wb1A2Oo2dv5d@kwain \
    --to=atenart@kernel.org \
    --cc=alice@isovalent.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eilaimemedsnaimel@gmail.com \
    --cc=haijun.liu@mediatek.com \
    --cc=horms@kernel.org \
    --cc=hw.he@mediatek.com \
    --cc=imv4bel@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=lambert.wang@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=willemb@google.com \
    --cc=xiayu.zhang@mediatek.com \
    --cc=zhaoping.shu@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.