From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
pablo@netfilter.org, netdev@vger.kernel.org, ooppublic@163.com
Subject: Re: [PATCH net] ipv4: fix ip option filtering for locally generated fragments
Date: Mon, 24 Jan 2022 12:10:10 +0000 [thread overview]
Message-ID: <164302621083.19022.13176797373164334866.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220122005731.2115923-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 21 Jan 2022 16:57:31 -0800 you wrote:
> During IP fragmentation we sanitize IP options. This means overwriting
> options which should not be copied with NOPs. Only the first fragment
> has the original, full options.
>
> ip_fraglist_prepare() copies the IP header and options from previous
> fragment to the next one. Commit 19c3401a917b ("net: ipv4: place control
> buffer handling away from fragmentation iterators") moved sanitizing
> options before ip_fraglist_prepare() which means options are sanitized
> and then overwritten again with the old values.
>
> [...]
Here is the summary with links:
- [net] ipv4: fix ip option filtering for locally generated fragments
https://git.kernel.org/netdev/net/c/27a8caa59bab
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:[~2022-01-24 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 0:57 [PATCH net] ipv4: fix ip option filtering for locally generated fragments Jakub Kicinski
2022-01-24 12: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=164302621083.19022.13176797373164334866.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ooppublic@163.com \
--cc=pablo@netfilter.org \
--cc=yoshfuji@linux-ipv6.org \
/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;
as well as URLs for NNTP newsgroup(s).