From: Ido Schimmel <idosch@nvidia.com>
To: Ren Wei <weir@nebusec.ai>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, tom@herbertland.com, vega@nebusec.ai,
petalzu987@gmail.com
Subject: Re: [PATCH net v2 1/1] ip6_tunnel: snapshot encap in xmit
Date: Sun, 9 Aug 2026 16:46:13 +0300 [thread overview]
Message-ID: <20260809134613.GA2478309@shredder> (raw)
In-Reply-To: <b58876297f7d45de008f2e94b6ecab8b2ed84d21.1786088695.git.petalzu987@gmail.com>
On Sat, Aug 08, 2026 at 04:40:49PM +0800, Ren Wei wrote:
> @@ -1202,6 +1204,15 @@ int ip6_tnl_xmit(struct sk_buff *skb, struct net_device *dev, __u8 dsfield,
> t->parms.name);
> goto tx_err_dst_release;
> }
> +
> + /* Can tear, but hlen and build_header() use the same snapshot. */
> + ipencap = data_race(t->encap);
> + encap_hlen = ip6_encap_hlen(&ipencap);
> + if (unlikely(encap_hlen < 0))
> + goto tx_err_dst_release;
> + psh_hlen = sizeof(struct ipv6hdr) + encap_hlen;
> + max_headroom = psh_hlen;
> +
> mtu = dst6_mtu(dst) - eth_hlen - psh_hlen - t->tun_hlen;
> if (encap_limit >= 0) {
> max_headroom += 8;
[...]
> @@ -1272,10 +1283,10 @@ int ip6_tnl_xmit(struct sk_buff *skb, struct net_device *dev, __u8 dsfield,
> * needed_headroom if necessary.
> */
> max_headroom = LL_RESERVED_SPACE(tdev) + sizeof(struct ipv6hdr)
> - + dst->header_len + t->hlen;
> + + dst->header_len + t->tun_hlen + encap_hlen;
Sashiko is correct that 'hlen = tun_hlen + encap_hlen' doesn't hold for
ip6erspan which accounts for the ERSPAN header length separately (not
part of tun_hlen).
There is no need to touch this line since it's irrelevant to the fix.
The needed headroom was already calculated correctly earlier
('psh_hlen') and guaranteed to be available in the skb by
skb_realloc_headroom(), when needed.
> ip_tunnel_adj_headroom(dev, max_headroom);
>
> - err = ip6_tnl_encap(skb, t, &proto, fl6);
> + err = ip6_tnl_encap(skb, &ipencap, &proto, fl6);
> if (err)
> return err;
>
> --
> 2.34.1
prev parent reply other threads:[~2026-08-09 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 8:40 [PATCH net v2 0/1] ip6_tunnel: snapshot encap in xmit Ren Wei
2026-08-08 8:40 ` [PATCH net v2 1/1] " Ren Wei
2026-08-08 19:38 ` Kuniyuki Iwashima
2026-08-09 12:33 ` Ido Schimmel
2026-08-24 19:47 ` Artem Lytkin
2026-08-25 7:23 ` Zixuan Chai
2026-08-25 9:08 ` Artem Lytkin
2026-08-09 13:46 ` Ido Schimmel [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=20260809134613.GA2478309@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=petalzu987@gmail.com \
--cc=tom@herbertland.com \
--cc=vega@nebusec.ai \
--cc=weir@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