From: patchwork-bot+netdevbpf@kernel.org
To: Joshua Washington <joshwash@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
stable@kernel.org, pkaligineedi@google.com,
hramamurthy@google.com, willemb@google.com, edumazet@google.com,
avagin@gmail.com, jeroendb@google.com, shailend@google.com,
pabeni@redhat.com, rushilg@google.com, csully@google.com,
bcf@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] gve: ignore nonrelevant GSO type bits when processing TSO headers
Date: Wed, 12 Jun 2024 03:00:33 +0000 [thread overview]
Message-ID: <171816123349.11889.11987638058865473120.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240610225729.2985343-1-joshwash@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 10 Jun 2024 15:57:18 -0700 you wrote:
> From: Joshua Washington <joshwash@google.com>
>
> TSO currently fails when the skb's gso_type field has more than one bit
> set.
>
> TSO packets can be passed from userspace using PF_PACKET, TUNTAP and a
> few others, using virtio_net_hdr (e.g., PACKET_VNET_HDR). This includes
> virtualization, such as QEMU, a real use-case.
>
> [...]
Here is the summary with links:
- [net,v3] gve: ignore nonrelevant GSO type bits when processing TSO headers
https://git.kernel.org/netdev/net/c/1b9f75634441
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:[~2024-06-12 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 19:21 [PATCH net] gve: ignore nonrelevant GSO type bits when processing TSO headers joshwash
2024-06-06 21:53 ` Willem de Bruijn
2024-06-06 22:16 ` Andrei Vagin
2024-06-07 6:09 ` [PATCH net v2] " joshwash
2024-06-07 6:35 ` Eric Dumazet
2024-06-07 14:07 ` Willem de Bruijn
2024-06-10 22:57 ` [PATCH net v3] " joshwash
2024-06-11 0:27 ` Jakub Kicinski
2024-06-11 2:26 ` Joshua Washington
2024-06-11 2:35 ` Jakub Kicinski
2024-06-12 3:00 ` 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=171816123349.11889.11987638058865473120.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=avagin@gmail.com \
--cc=bcf@google.com \
--cc=csully@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=stable@kernel.org \
--cc=willemb@google.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).