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, mst@redhat.com,
jasowang@redhat.com, arefev@swemel.ru, alexander.duyck@gmail.com,
willemb@google.com, stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: drop bad gso csum_start and offset in virtio_net_hdr
Date: Wed, 31 Jul 2024 02:00:34 +0000 [thread overview]
Message-ID: <172239123454.15322.14803499177982622377.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240729201108.1615114-1-willemdebruijn.kernel@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 29 Jul 2024 16:10:12 -0400 you wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> Tighten csum_start and csum_offset checks in virtio_net_hdr_to_skb
> for GSO packets.
>
> The function already checks that a checksum requested with
> VIRTIO_NET_HDR_F_NEEDS_CSUM is in skb linear. But for GSO packets
> this might not hold for segs after segmentation.
>
> [...]
Here is the summary with links:
- [net,v2] net: drop bad gso csum_start and offset in virtio_net_hdr
https://git.kernel.org/netdev/net/c/89add40066f9
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-07-31 2:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 20:10 [PATCH net v2] net: drop bad gso csum_start and offset in virtio_net_hdr Willem de Bruijn
2024-07-31 2:00 ` patchwork-bot+netdevbpf [this message]
2024-09-06 14:35 ` Szabolcs Nagy
2024-09-06 15:52 ` Willem de Bruijn
2024-09-08 20:09 ` Willem de Bruijn
2024-09-08 20:43 ` Michael S. Tsirkin
2024-09-09 2:33 ` Jason Wang
2024-09-09 3:02 ` Willem de Bruijn
2024-09-09 3:24 ` Jason Wang
2024-09-09 3:39 ` Willem de Bruijn
2024-09-09 4:14 ` Jason Wang
2024-09-09 15:20 ` Willem de Bruijn
2024-09-09 21:09 ` Willem de Bruijn
2024-09-10 1:12 ` Willem de Bruijn
2024-09-09 9:45 ` Szabolcs Nagy
2024-09-09 11:14 ` Mark Brown
2024-09-09 15:14 ` Sudeep Holla
2024-09-09 15:21 ` Willem de Bruijn
2024-09-09 10:13 ` Yury Khrustalev
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=172239123454.15322.14803499177982622377.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=arefev@swemel.ru \
--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=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).