mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kyle Zeng <kylebot@openai.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
	linux-kernel@vger.kernel.org, outbounddisclosures@openai.com
Subject: Re: [PATCH] ipv4: keep XFRM headers out of corked skb lengths
Date: Mon, 09 Nov 2026 23:20:05 +0000	[thread overview]
Message-ID: <179426640593.3539542.14588290897473786391.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261030042229.74068-1-kylebot@openai.com>

Hello:

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

On Thu, 29 Oct 2026 21:22:29 -0700 you wrote:
> __ip_append_data() allocates space for dst.header_len in the first skb,
> but includes that space in skb->len until __ip_make_skb() pulls it.
> Fragment accounting uses an MTU that already excludes the XFRM headers.
> As a result, the next skb can have a fraggap larger than its capped
> datalen, and skb_copy_and_csum_bits() can overwrite its shared info.
> 
> For example, five AH tunnel states can reserve 500 bytes while leaving
> an effective MTU of 348. With 40 bytes of IPv4 options, the second skb
> has room for 288 bytes of fragment data but receives a 500-byte gap
> copy. The overwritten shared info is subsequently consumed by the skb
> release paths.
> 
> [...]

Here is the summary with links:
  - ipv4: keep XFRM headers out of corked skb lengths
    https://git.kernel.org/netdev/net/c/0f47fce51a98

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-11-09 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  4:22 Kyle Zeng
2026-10-30  4:24 ` netdev-bot+sinfo
2026-11-09 23: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=179426640593.3539542.14588290897473786391.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dsahern@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kylebot@openai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=outbounddisclosures@openai.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®