Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?dGVuY2VudG9zX3NlY3VyZShUZW5jZW50T1PlronlhajlhazlhbHpgq7nrrEpIDx0?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
	=?utf-8?b?ZW5jZW50b3Nfc2VjdXJlQHRlbmNlbnQuY29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
	pabeni@redhat.com, kuba@kernel.org, willemb@google.com,
	willemdebruijn.kernel@gmail.com, klassert@kernel.org,
	steffen.klassert@secunet.com, edumazet@kernel.org
Subject: Re: [PATCH net v2 0/2] ipv4: fix fragment length accounting
Date: Mon, 09 Nov 2026 23:20:07 +0000	[thread overview]
Message-ID: <179426640716.3539542.13397803141946938999.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <36C40B0A9C6336F3+ipv4.6d58afc075934322860394a26ceaa2e8.0@tencent.com>

Hello:

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

On Thu, 05 Nov 2026 15:34:36 +0800 you wrote:
> This series corrects fragment length accounting in __ip_append_data().
> Patch 1 reserves the XFRM bundle header space as headroom. Patch 2
> rejects an append when the transport header and moved tail do not fit;
> it also addresses the independently reachable ICMP Timestamp case.
> 
> Changes since the initial public posting:
> - Patch 1: correct the skb->len/fraggap explanation, clarify IPv6's
>   dst_exthdrlen terminology, and scope the layout comparison to the
>   same skb setup inputs. Add Willem's Reviewed-by.
> - Patch 2: describe the ICMP Timestamp corruption path, distinguish
>   negative copy from unsigned pagedlen wrap, update the subject and
>   Fixes tag, and remove the unrelated XFRM Reported-by.
> - No code changes in either patch.
> 
> [...]

Here is the summary with links:
  - [net,v2,2/2] net/ipv4: reject appends with negative fragment copy
    (no matching commit)
  - [net,v2,1/2] net/ipv4: reserve exthdrlen as headroom instead of counting it in skb->len
    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



      reply	other threads:[~2026-11-09 23:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  7:34 [PATCH net v2 0/2] ipv4: fix fragment length accounting =?gb18030?B?dGVuY2VudG9zX3NlY3VyZShUZW5jZW50T1Owssiruau5stPKz+Qp?=
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=179426640716.3539542.13397803141946938999.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?b?ZW5jZW50b3Nfc2VjdXJlQHRlbmNlbnQuY29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc==?utf-8?b?dGVuY2VudG9zX3NlY3VyZShUZW5jZW50T1PlronlhajlhazlhbHpgq7nrrEpIDx0?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=dsahern@kernel.org \
    --cc=edumazet@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=klassert@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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