From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, stable@vger.kernel.org,
nsz@port70.net, mst@redhat.com, jasowang@redhat.com,
yury.khrustalev@arm.com, broonie@kernel.org,
sudeep.holla@arm.com, willemb@google.com
Subject: Re: [PATCH net v2] net: tighten bad gso csum offset check in virtio_net_hdr
Date: Thu, 12 Sep 2024 03:50:32 +0000 [thread overview]
Message-ID: <172611303278.1155279.7529343759399264927.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240910213553.839926-1-willemdebruijn.kernel@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Sep 2024 17:35:35 -0400 you wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> The referenced commit drops bad input, but has false positives.
> Tighten the check to avoid these.
>
> The check detects illegal checksum offload requests, which produce
> csum_start/csum_off beyond end of packet after segmentation.
>
> [...]
Here is the summary with links:
- [net,v2] net: tighten bad gso csum offset check in virtio_net_hdr
https://git.kernel.org/netdev/net/c/6513eb3d3191
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-09-12 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 21:35 [PATCH net v2] net: tighten bad gso csum offset check in virtio_net_hdr Willem de Bruijn
2024-09-12 3:50 ` patchwork-bot+netdevbpf [this message]
2024-09-12 13:39 ` Sudeep Holla
2024-09-12 15:30 ` Willem de Bruijn
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=172611303278.1155279.7529343759399264927.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nsz@port70.net \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yury.khrustalev@arm.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;
as well as URLs for NNTP newsgroup(s).