Netdev List
 help / color / mirror / Atom feed
From: Jianbo Liu <jianbol@nvidia.com>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<kuba@kernel.org>, <steffen.klassert@secunet.com>,
	Cosmin Ratiu <cratiu@nvidia.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH ipsec v2 2/2] xfrm: Determine inner GSO type from packet inner protocol
Date: Tue, 28 Oct 2025 09:47:31 +0800	[thread overview]
Message-ID: <b92ec23d-f877-4dc3-a95f-c9b66120686c@nvidia.com> (raw)
In-Reply-To: <aP-QvtNf-Vp5oHLX@krikkit>



On 10/27/2025 11:33 PM, Sabrina Dubroca wrote:
> 2025-10-27, 04:40:59 +0200, Jianbo Liu wrote:
>> The GSO segmentation functions for ESP tunnel mode
>> (xfrm4_tunnel_gso_segment and xfrm6_tunnel_gso_segment) were
>> determining the inner packet's L2 protocol type by checking the static
>> x->inner_mode.family field from the xfrm state.
>>
>> This is unreliable. In tunnel mode, the state's actual inner family
>> could be defined by x->inner_mode.family or by
>> x->inner_mode_iaf.family. Checking only the former can lead to a
>> mismatch with the actual packet being processed, causing GSO to create
>> segments with the wrong L2 header type.
>>
>> This patch fixes the bug by deriving the inner mode directly from the
>> packet's inner protocol stored in XFRM_MODE_SKB_CB(skb)->protocol.
>>
>> Fixes: 26dbd66eab80 ("esp: choose the correct inner protocol for GSO on inter address family tunnels")
>> Signed-off-by: Jianbo Liu <jianbol@nvidia.com>
>> Reviewed-by: Cosmin Ratiu <cratiu@nvidia.com>
>> ---
>> V2:
>>   - Change subject prefix, and send to "ipsec".
>>   - Add Fixes tag.
>>
>>   net/ipv4/esp4_offload.c | 6 ++++--
>>   net/ipv6/esp6_offload.c | 6 ++++--
>>   2 files changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/net/ipv4/esp4_offload.c b/net/ipv4/esp4_offload.c
>> index e0d94270da28..05828d4cb6cd 100644
>> --- a/net/ipv4/esp4_offload.c
>> +++ b/net/ipv4/esp4_offload.c
>> @@ -122,8 +122,10 @@ static struct sk_buff *xfrm4_tunnel_gso_segment(struct xfrm_state *x,
>>   						struct sk_buff *skb,
>>   						netdev_features_t features)
>>   {
>> -	__be16 type = x->inner_mode.family == AF_INET6 ? htons(ETH_P_IPV6)
>> -						       : htons(ETH_P_IP);
>> +	const struct xfrm_mode *inner_mode = xfrm_ip2inner_mode(x,
>> +					XFRM_MODE_SKB_CB(skb)->protocol);
> 
> I don't think this is correct. inner_mode_iaf is not always set by
> __xfrm_init_state, only when we have a AF_UNSPEC selector, which is
> not always the case for cross-family tunnels. So we would end up with
> inner_mode->family = 0 here, and pass the wrong type to
> skb_eth_gso_segment.
> 
> Other users of xfrm_ip2inner_mode (in ip_vti/ip6_vti, xfrmi) only call
> it when we have an AF_UNSPEC selector, then we know inner_mode_iaf is
> valid and can be used. Otherwise, the selector (ie x->inner_mode)
> should have the right family for the packet (and all callers of
> xfrm_ip2inner_mode use x->inner_mode when the selector is not
> AF_UNSPEC).
> 
> 
> Maybe it would be better to move the AF_UNSPEC check into
> xfrm_ip2inner_mode, something like:
> 
> static inline const struct xfrm_mode *xfrm_ip2inner_mode(struct xfrm_state *x, int ipproto)
> {
> 	if (x->sel.family != AF_UNSPEC)
> 		return &x->inner_mode;
> 
> 	if ((ipproto == IPPROTO_IPIP && x->props.family == AF_INET) ||
> 	    (ipproto == IPPROTO_IPV6 && x->props.family == AF_INET6))
> 		return &x->inner_mode;
> 	else
> 		return &x->inner_mode_iaf;
> }
> 
> 
> since that's what all the callers are doing anyway?
> 
> Then it would be valid to use xfrm_ip2inner_mode like you're doing.

It makes sense. I will submit v3 soon. Thanks!

> 


      reply	other threads:[~2025-10-28  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27  2:40 [PATCH ipsec v2 0/2] xfrm: Correct inner packet family determination Jianbo Liu
2025-10-27  2:40 ` [PATCH ipsec v2 1/2] xfrm: Check inner packet family directly from skb_dst Jianbo Liu
2025-10-27  2:40 ` [PATCH ipsec v2 2/2] xfrm: Determine inner GSO type from packet inner protocol Jianbo Liu
2025-10-27 15:33   ` Sabrina Dubroca
2025-10-28  1:47     ` Jianbo Liu [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=b92ec23d-f877-4dc3-a95f-c9b66120686c@nvidia.com \
    --to=jianbol@nvidia.com \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --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