From: Ido Schimmel <idosch@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>, zhilinz@nebusec.ai
Cc: Zhiling Zou <zhilinz@nebusec.ai>,
netdev@vger.kernel.org, dsahern@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
tom@herbertland.com, vega@nebusec.ai
Subject: Re: [PATCH net 1/1] ip6_tunnel: use skb_cow_head() in ip6_tnl_xmit()
Date: Thu, 6 Aug 2026 11:52:14 +0300 [thread overview]
Message-ID: <20260806085214.GA1748060@shredder> (raw)
In-Reply-To: <20260805172902.27c9bde0@kernel.org>
On Wed, Aug 05, 2026 at 05:29:02PM -0700, Jakub Kicinski wrote:
> On Wed, 5 Aug 2026 12:07:21 +0300 Ido Schimmel wrote:
> > __gre6_xmit() and ip6erspan_tunnel_xmit() already call skb_cow_head()
> > before calling ip6_tnl_xmit().
>
> Probably just me but can't they all be buggy?
> PKTGEN likes to send shared skbs around in funny ways.
> Can we get a good explanation in the commit msg or maybe let's
> keep the check?
ip6_tnl_xmit() is accessible via two Ethernet devices (pktgen doesn't
support other types) and they both clear IFF_TX_SKB_SHARING, so if
pktgen sends them shared skbs, I would say that it's a pktgen bug and
not a reason to block this patch. Note that pktgen is not available to
unprivileged users, so it's a less severe bug.
The patch also makes ip6_tnl_xmit() consistent with its IPv4 counterpart
(ip_tunnel_xmit()) which is already using skb_cow_head().
Zhiling, please add a note in the commit message that ip6gretap and
ip6erspan do not expect to be handed shared skbs given that they clear
IFF_TX_SKB_SHARING.
next prev parent reply other threads:[~2026-08-06 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 5:34 [PATCH net 0/1] ip6_tunnel: use skb_cow_head() in ip6_tnl_xmit() Zhiling Zou
2026-08-03 5:34 ` [PATCH net 1/1] " Zhiling Zou
2026-08-05 9:07 ` Ido Schimmel
2026-08-06 0:29 ` Jakub Kicinski
2026-08-06 8:52 ` Ido Schimmel [this message]
2026-08-06 9:06 ` zhilin zou
2026-08-06 16:28 ` Paolo Abeni
2026-08-06 18:19 ` Ido Schimmel
2026-08-07 8:31 ` Paolo Abeni
2026-08-09 7:57 ` Ido Schimmel
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=20260806085214.GA1748060@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tom@herbertland.com \
--cc=vega@nebusec.ai \
--cc=zhilinz@nebusec.ai \
/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