From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, david.lebrun@uclouvain.be,
steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
dsahern@kernel.org, hazleycryilis@gmail.com,
hangbin.liu@linux.dev, stefano.salsano@uniroma2.it,
liuhangbin@kylinos.cn
Subject: Re: [PATCH net v2] seg6: fix transport header for inner IPv4 with IP options
Date: Fri, 30 Oct 2026 00:10:05 +0000 [thread overview]
Message-ID: <179331900509.763714.8850893492667145645.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261028171511.35-1-andrea.mayer@uniroma2.it>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 28 Oct 2026 18:15:11 +0100 you wrote:
> The End.DT4, End.DT46 (its IPv4 path only) and End.DX4 behaviors set the
> transport header of the decapsulated IPv4 packet at a fixed 20 bytes, the
> size of an IPv4 header without options. They do not validate the header
> length either. With options, the transport header points at the first
> option byte. The effects include:
> - ping -R sends an echo request with a 60-byte IPv4 header to a local
> address through an End.DT4 or an End.DX4 SID. Since icmp_rcv()
> computes the ICMP checksum from the first option byte, the request
> fails the check and is counted in IcmpInCsumErrors.
> - A UDP datagram can reach a port that an iptables rule drops. The rule
> checks the UDP header after the full IPv4 header, while the socket
> lookup reads it at the fixed 20-byte offset.
> - With an inbound AH state, ah_input() reads the AH header at the fixed
> 20-byte offset, but copies the IPv4 header over it with the length in
> the IHL field. A packet shorter than that length can make ah_input()
> write past the end of the data, into skb_shared_info when the skb has
> no tailroom.
>
> [...]
Here is the summary with links:
- [net,v2] seg6: fix transport header for inner IPv4 with IP options
https://git.kernel.org/netdev/net/c/5838f10563d5
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-10-30 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 17:15 Andrea Mayer
2026-10-30 0:10 ` 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=179331900509.763714.8850893492667145645.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=david.lebrun@uclouvain.be \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=hangbin.liu@linux.dev \
--cc=hazleycryilis@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefano.salsano@uniroma2.it \
--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
all inboxes | Powered by JetHome®