From: Aaron Esau <aaron1esau@gmail.com>
To: imv4bel@gmail.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, sultan@kerneltoast.com,
sd@queasysnail.net, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, dsahern@kernel.org,
netdev@vger.kernel.org, stable@vger.kernel.org,
Aaron Esau <aaron1esau@gmail.com>
Subject: Re: [PATCH net v4] net: skbuff: propagate shared-frag marker through frag-transfer helpers
Date: Fri, 15 May 2026 11:41:21 -0500 [thread overview]
Message-ID: <20260515164121.2608076-1-aaron1esau@gmail.com> (raw)
In-Reply-To: <aga1VyHpHaUhnGZa@v4bel>
skb_segment() propagates SKBFL_SHARED_FRAG from head_skb only. When
segments pull frags from frag_list members, the flag is never
propagated from those members into the segment skb.
There are two miss sites:
1. Line ~4986: a new nskb propagates only from head_skb, but frag_skb
may already point to a list_skb carried over from the previous
segment's iteration (i, nfrags, frag_skb persist across the outer
do/while).
2. When the inner loop exhausts head_skb frags and switches to a
list_skb (line ~4999-5002), frag_skb is updated but its
SKBFL_SHARED_FRAG is not propagated into nskb.
Your v4 GRO fix means head_skb will normally carry the flag, so
skb_segment() picks it up indirectly. But skb_segment() itself should
propagate from frag_list members directly --- otherwise any non-GRO
frag_list producer re-exposes the gap.
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -4986,7 +4986,8 @@ struct sk_buff *skb_segment(struct sk_buff *head_skb,
- skb_shinfo(nskb)->flags |= skb_shinfo(head_skb)->flags &
- SKBFL_SHARED_FRAG;
+ skb_shinfo(nskb)->flags |= (skb_shinfo(head_skb)->flags |
+ skb_shinfo(frag_skb)->flags) &
+ SKBFL_SHARED_FRAG;
if (skb_zerocopy_clone(nskb, frag_skb, GFP_ATOMIC))
@@ -5000,6 +5001,8 @@ struct sk_buff *skb_segment(struct sk_buff *head_skb,
frag = skb_shinfo(list_skb)->frags;
frag_skb = list_skb;
+ skb_shinfo(nskb)->flags |= skb_shinfo(frag_skb)->flags & SKBFL_SHARED_FRAG;
+
if (!skb_headlen(list_skb)) {
BUG_ON(!nfrags);
} else {
Site 1 covers segments that start mid-list_skb (frag_skb carried from
the previous segment). Site 2 covers segments that switch from
head_skb frags to list_skb frags mid-construction.
Fixes: cef401de7be8 ("net: fix possible wrong checksum generation")
next prev parent reply other threads:[~2026-05-15 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 5:55 [PATCH net v4] net: skbuff: propagate shared-frag marker through frag-transfer helpers Hyunwoo Kim
2026-05-15 6:07 ` Hyunwoo Kim
2026-05-15 6:26 ` Sultan Alsawaf
2026-05-15 6:36 ` Hyunwoo Kim
2026-05-15 15:11 ` Hyunwoo Kim
2026-05-15 16:41 ` Aaron Esau [this message]
2026-05-15 20:22 ` Hyunwoo Kim
2026-05-15 21:36 ` Hyunwoo Kim
2026-05-16 0:08 ` Jakub Kicinski
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=20260515164121.2608076-1-aaron1esau@gmail.com \
--to=aaron1esau@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=imv4bel@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=sultan@kerneltoast.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.