netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jianbo Liu <jianbol@nvidia.com>
To: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<kuba@kernel.org>, <steffen.klassert@secunet.com>
Cc: Jianbo Liu <jianbol@nvidia.com>
Subject: [PATCH net-next 0/3] xfrm: Correct inner packet family determination
Date: Fri, 24 Oct 2025 05:31:34 +0300	[thread overview]
Message-ID: <20251024023931.65002-1-jianbol@nvidia.com> (raw)

This series contains three 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.

Jianbo Liu (3):
  xfrm: Remove redundant state inner mode check
  xfrm: Check inner packet family directly from skb_dst
  xfrm: Determine inner GSO type from packet inner protocol

 net/ipv4/esp4_offload.c        | 6 ++++--
 net/ipv4/ip_vti.c              | 8 +-------
 net/ipv6/esp6_offload.c        | 6 ++++--
 net/ipv6/ip6_vti.c             | 8 +-------
 net/xfrm/xfrm_device.c         | 2 +-
 net/xfrm/xfrm_interface_core.c | 8 +-------
 net/xfrm/xfrm_output.c         | 2 +-
 net/xfrm/xfrm_policy.c         | 9 ++-------
 8 files changed, 15 insertions(+), 34 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-10-24  2:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  2:31 Jianbo Liu [this message]
2025-10-24  2:31 ` [PATCH net-next 1/3] xfrm: Remove redundant state inner mode check Jianbo Liu
2025-10-24  2:31 ` [PATCH net-next 2/3] xfrm: Check inner packet family directly from skb_dst Jianbo Liu
2025-10-24 11:26   ` Sabrina Dubroca
2025-10-27  1:50     ` Jianbo Liu
2025-10-24  2:31 ` [PATCH net-next 3/3] xfrm: Determine inner GSO type from packet inner protocol Jianbo Liu

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=20251024023931.65002-1-jianbol@nvidia.com \
    --to=jianbol@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    /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).