From: patchwork-bot+netdevbpf@kernel.org
To: Matt Vollrath <tactii@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
willemb@google.com, alexanderduyck@fb.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next v2] net: reset transport_header for ndo_features_check
Date: Thu, 12 Nov 2026 10:40:04 +0000 [thread overview]
Message-ID: <179448000468.2004564.5316033987068882580.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106172925.3718103-1-tactii@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 6 Nov 2026 12:29:25 -0500 you wrote:
> For CHECKSUM_PARTIAL skbs, validate_xmit_skb() resets
> transport_header (inner_transport_header for encapsulated skbs)
> from csum_start, but only after netif_skb_features() has called
> ndo_features_check().
>
> The hook can therefore see a transport_header left elsewhere by
> the receive path, while ndo_start_xmit() sees the reset one. For
> example, ip6_rcv_core() leaves it after the fixed header of
> forwarded IPv6 packets with destination options or a routing
> header, and seg6, rpl and ioam6 point it at the header they insert.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: reset transport_header for ndo_features_check
https://git.kernel.org/netdev/net-next/c/f4564d298418
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-12 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:29 [PATCH net-next v2] net: reset transport_header for ndo_features_check Matt Vollrath
2026-11-12 10:40 ` 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=179448000468.2004564.5316033987068882580.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tactii@gmail.com \
--cc=willemb@google.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