From: patchwork-bot+netdevbpf@kernel.org
To: Gal Pressman <gal@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, netdev@vger.kernel.org,
horms@kernel.org, willemb@google.com, dtatulea@nvidia.com,
alice@isovalent.com
Subject: Re: [PATCH net v2 0/2] udp: gso: Fix __udp_gso_segment() after GSO_PARTIAL UDP length change
Date: Wed, 20 May 2026 22:20:07 +0000 [thread overview]
Message-ID: <177931560764.3775142.17228942872118757951.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260518062250.3019914-1-gal@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 18 May 2026 09:22:48 +0300 you wrote:
> This series fixes two issues introduced by commit b10b446ce7ad ("udp:
> gso: Use single MSS length in UDP header for GSO_PARTIAL"), which
> switched __udp_gso_segment() to write the single MSS length into the UDP
> header for GSO_PARTIAL skbs.
>
> Patch 1 (from Alice) fixes the UDP checksum adjustment in
> __udp_gso_segment().
> The patch adjusts the checksum by the correct delta, and since msslen
> and newlen become equivalent before the loop, drops one of the two
> variables to simplify the code.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] udp: gso: Fix handling checksum in __udp_gso_segment
https://git.kernel.org/netdev/net/c/5f17ae0f595a
- [net,v2,2/2] udp: Fix UDP length on last GSO_PARTIAL segment
https://git.kernel.org/netdev/net/c/78effd896eee
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-05-20 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 6:22 [PATCH net v2 0/2] udp: gso: Fix __udp_gso_segment() after GSO_PARTIAL UDP length change Gal Pressman
2026-05-18 6:22 ` [PATCH net v2 1/2] udp: gso: Fix handling checksum in __udp_gso_segment Gal Pressman
2026-05-18 6:22 ` [PATCH net v2 2/2] udp: Fix UDP length on last GSO_PARTIAL segment Gal Pressman
2026-05-20 1:12 ` Jakub Kicinski
2026-05-20 16:34 ` Gal Pressman
2026-05-20 22:05 ` Jakub Kicinski
2026-05-20 22:20 ` 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=177931560764.3775142.17228942872118757951.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alice@isovalent.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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