From: Steffen Klassert <steffen.klassert@secunet.com>
To: "Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v5 0/2] xfrm: fix IPv6 atomic fragment policy handling
Date: Fri, 20 Nov 2026 07:46:31 +0100 [thread overview]
Message-ID: <av_sx9bxaRqhuRlQ@gauss4> (raw)
In-Reply-To: <20261111231853.2504833-2-Jeremy.Jean@oss.cyber.gouv.fr>
On Wed, Nov 11, 2026 at 11:18:51PM +0000, Jérémy Jean wrote:
> This series fixes two IPv6 fragment issues in XFRM session decoding.
>
> Patch 1 restores upper-layer protocol decoding for first fragments.
> Patch 2 restores ports, ICMPv6 type and code, and GRE keys for atomic
> fragments, while leaving them unset for real fragments.
>
> Changes in v5 after a review from Sashiko:
> - Patch 1: unchanged.
> - Patch 2: use the IPv6 walk offset for transport headers before
> skb->data, preserve flow-dissector offsets otherwise.
>
> Jérémy Jean (2):
> xfrm: fix IPv6 first-fragment protocol decode
> xfrm: fix selector matching for IPv6 atomic fragments
Series applied, thanks Jérémy!
prev parent reply other threads:[~2026-11-20 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 23:18 [PATCH net v5 0/2] xfrm: fix IPv6 atomic fragment policy handling Jérémy Jean
2026-11-11 23:18 ` [PATCH net v5 1/2] xfrm: fix IPv6 first-fragment protocol decode Jérémy Jean
2026-11-11 23:18 ` [PATCH net v5 2/2] xfrm: fix selector matching for IPv6 atomic fragments Jérémy Jean
2026-11-11 23:27 ` [PATCH net v5 0/2] xfrm: fix IPv6 atomic fragment policy handling netdev-bot+sinfo
2026-11-20 6:46 ` 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=av_sx9bxaRqhuRlQ@gauss4 \
--to=steffen.klassert@secunet.com \
--cc=Jeremy.Jean@oss.cyber.gouv.fr \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=idosch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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