From: Steffen Klassert <steffen.klassert@secunet.com>
To: Cosmin Ratiu <cratiu@nvidia.com>
Cc: <netdev@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Shuah Khan <shuah@kernel.org>, Nimrod Oren <noren@nvidia.com>,
Carolina Jubran <cjubran@nvidia.com>,
Gal Pressman <gal@nvidia.com>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH ipsec 0/3] xfrm: Don't clobber inner headers when already set
Date: Wed, 29 Apr 2026 08:32:03 +0200 [thread overview]
Message-ID: <afGl40FUuqiwV-B7@secunet.com> (raw)
In-Reply-To: <20260422140648.3877129-1-cratiu@nvidia.com>
On Wed, Apr 22, 2026 at 05:06:45PM +0300, Cosmin Ratiu wrote:
> Commit [1] exposed an existing issue in xfrm which broke tunneling
> protocols over IPsec (e.g. VXLAN over IPsec).
>
> This series fixes that and adds a test which exercises VXLAN over IPsec.
> For details please see the individual patches.
>
> [1] commit 7fb4c1967011 ("net: pull headers in qdisc_pkt_len_segs_init()")
>
> Cosmin Ratiu (3):
> tools/selftests: Use a sensible timeout value for iperf3 client
> tools/selftests: Add a VXLAN+IPsec traffic test
> xfrm: Don't clobber inner headers when already set
Series applied, thanks a lot Cosmin!
prev parent reply other threads:[~2026-04-29 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 14:06 [PATCH ipsec 0/3] xfrm: Don't clobber inner headers when already set Cosmin Ratiu
2026-04-22 14:06 ` [PATCH ipsec 1/3] tools/selftests: Use a sensible timeout value for iperf3 client Cosmin Ratiu
2026-04-22 14:06 ` [PATCH ipsec 2/3] tools/selftests: Add a VXLAN+IPsec traffic test Cosmin Ratiu
2026-04-22 14:06 ` [PATCH ipsec 3/3] xfrm: Don't clobber inner headers when already set Cosmin Ratiu
2026-04-29 6:32 ` Steffen Klassert [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=afGl40FUuqiwV-B7@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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