All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	andrew+netdev@lunn.ch, xietangxin@yeah.net, willemb@google.com,
	stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: extend IPv6 exthdr detection of tunneled packets
Date: Wed, 30 Sep 2026 01:20:06 +0000	[thread overview]
Message-ID: <179073120652.1194536.6933044569740005192.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260926140506.2335137-1-willemdebruijn.kernel@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 26 Sep 2026 10:04:54 -0400 you wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> Commit c4336a07eb6b ("net: correctly handle tunneled traffic on IPV6_CSUM
> GSO fallback") split skb_gso_has_extension_hdr() into mutually exclusive
> branches on skb->encapsulation. This did not yet address all paths:
> 
> 1. With skb->encapsulation set, the outer header is not checked. IPv6
>    tunnels such as ip6_gre and ip6_tunnel add an outer Destination
>    Options header by default (encap_limit). Their GSO packets skip
>    software GSO, then skb_csum_hwoffload_help() sees the outer extension
>    header and calls skb_checksum_help() on the GSO skb, which warns and
>    drops it.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: extend IPv6 exthdr detection of tunneled packets
    https://git.kernel.org/netdev/net/c/5f0764cb1c81

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-30  1:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 14:04 [PATCH net v2] net: extend IPv6 exthdr detection of tunneled packets Willem de Bruijn
2026-09-29  0:07 ` netdev-bot+sashiko
2026-09-29  3:23   ` Willem de Bruijn
2026-09-30  1:20 ` patchwork-bot+netdevbpf [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=179073120652.1194536.6933044569740005192.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=xietangxin@yeah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.