From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, willemb@google.com,
steffen.klassert@secunet.com, tom@herbertland.com,
cenzhang@linux.microsoft.com,
AutonomousCodeSecurity@microsoft.com
Subject: Re: [PATCH net v4 0/2] net: gro: fix frag0 and remcsum handling
Date: Tue, 10 Nov 2026 02:54:45 +0000 [thread overview]
Message-ID: <179427928516.3612825.13177875895185674997.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104151042.1157782-1-edumazet@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Nov 2026 16:10:40 +0100 you wrote:
> Two GRO fixes for paths using remote checksum offload (VXLAN, GUE)
> and for NAPI_GRO_CB(skb)->frag0 after a pull.
>
> Patch 1 skips skb_gro_remcsum_cleanup() once the skb was merged,
> as grc->offset can no longer be trusted, and no longer builds
> fraglist packets with an adjusted inner checksum.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] net: gro: do not undo remote checksum offload on merged packets
https://git.kernel.org/netdev/net/c/c817ec1b0687
- [net,v4,2/2] net: gro: invalidate frag0 after a pull
https://git.kernel.org/netdev/net/c/98d949a15ff9
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-11-10 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:10 [PATCH net v4 0/2] net: gro: fix frag0 and remcsum handling Eric Dumazet
2026-11-04 15:10 ` [PATCH net v4 1/2] net: gro: do not undo remote checksum offload on merged packets Eric Dumazet
2026-11-04 15:10 ` [PATCH net v4 2/2] net: gro: invalidate frag0 after a pull Eric Dumazet
2026-11-10 2:54 ` 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=179427928516.3612825.13177875895185674997.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=AutonomousCodeSecurity@microsoft.com \
--cc=cenzhang@linux.microsoft.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=tom@herbertland.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