From: Steffen Klassert <steffen.klassert@secunet.com>
To: Jianbo Liu <jianbol@nvidia.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<kuba@kernel.org>, <sd@queasysnail.net>
Subject: Re: [PATCH ipsec v3 0/2] xfrm: Correct inner packet family determination
Date: Sat, 1 Nov 2025 13:29:01 +0100 [thread overview]
Message-ID: <aQX9DXuEBo7eBISZ@secunet.com> (raw)
In-Reply-To: <20251028023013.9836-1-jianbol@nvidia.com>
On Tue, Oct 28, 2025 at 04:22:46AM +0200, Jianbo Liu wrote:
> This series contains two patches addressing issues in the XFRM
> subsystem where the code incorrectly relied on static family fields
> from the xfrm_state instead of determining the family from the actual
> packet being processed.
>
> This was particularly problematic in tunnel mode scenarios when using
> states that could handle different inner families.
>
> V3:
> - Change xfrm_ip2inner_mode for the sel family specified
>
> V2:
> - The original first patch was sent separately to "ipsec-next"
>
> Jianbo Liu (2):
> xfrm: Check inner packet family directly from skb_dst
> xfrm: Determine inner GSO type from packet inner protocol
Applied, thaks a lot Jianbo!
prev parent reply other threads:[~2025-11-01 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 2:22 [PATCH ipsec v3 0/2] xfrm: Correct inner packet family determination Jianbo Liu
2025-10-28 2:22 ` [PATCH ipsec v3 1/2] xfrm: Check inner packet family directly from skb_dst Jianbo Liu
2025-10-28 14:27 ` Zhu Yanjun
2025-10-28 2:22 ` [PATCH ipsec v3 2/2] xfrm: Determine inner GSO type from packet inner protocol Jianbo Liu
2025-10-28 11:03 ` Sabrina Dubroca
2025-10-28 13:36 ` Jianbo Liu
2025-10-28 15:04 ` Sabrina Dubroca
2025-10-30 8:08 ` Steffen Klassert
2025-10-30 8:35 ` Jianbo Liu
2025-10-30 10:28 ` Sabrina Dubroca
2025-11-01 12:29 ` 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=aQX9DXuEBo7eBISZ@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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;
as well as URLs for NNTP newsgroup(s).