From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
eddiephillips@google.com, nktgrg@google.com,
hramamurthy@google.com, joshwash@google.com, willemb@google.com,
edumazet@kernel.org
Subject: Re: [PATCH net 0/2] gve: DQO: fix handling of out of range TSO MSS
Date: Thu, 24 Sep 2026 18:00:07 +0000 [thread overview]
Message-ID: <179027280738.1685480.3863257339813565809.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924004252.1196328-1-edumazet@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 24 Sep 2026 00:42:50 +0000 you wrote:
> The DQO TX path assumes that the MSS of a TSO packet is within the
> range supported by the device, [88, 9728].
>
> This holds for locally generated traffic, but not for packets coming
> from a tap or from a packet socket: virtio_net_hdr_to_skb() takes
> gso_size from user space and only enforces a minimum, layer 2
> forwarding does not check the MTU of GSO packets, and
> gso_features_check() bounds skb->len and gso_segs but never gso_size.
>
> [...]
Here is the summary with links:
- [net,1/2] gve: fix TX drop when GSO MSS is too small for hw
https://git.kernel.org/netdev/net/c/3b430ea62340
- [net,2/2] gve: DQO: reject TSO packets with an out of range MSS
https://git.kernel.org/netdev/net/c/296c83b5ccc8
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:[~2026-09-24 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 0:42 [PATCH net 0/2] gve: DQO: fix handling of out of range TSO MSS Eric Dumazet
2026-09-24 0:42 ` [PATCH net 1/2] gve: fix TX drop when GSO MSS is too small for hw Eric Dumazet
2026-09-24 0:42 ` [PATCH net 2/2] gve: DQO: reject TSO packets with an out of range MSS Eric Dumazet
2026-09-24 1:32 ` [PATCH net 0/2] gve: DQO: fix handling of out of range TSO MSS Harshitha Ramamurthy
2026-09-24 18: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=179027280738.1685480.3863257339813565809.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=eddiephillips@google.com \
--cc=edumazet@google.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--cc=pabeni@redhat.com \
--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