From: patchwork-bot+netdevbpf@kernel.org
To: Brad Fitzpatrick <bradfitz@tailscale.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
atenart@kernel.org, willemb@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 0/2] gre: merged GRE-over-FOU/GUE packets are dropped (bug report, possible fix)
Date: Sat, 17 Oct 2026 01:50:09 +0000 [thread overview]
Message-ID: <179220180976.1055958.15695873779763495713.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261011-bradfitz-gre-fou-gro-b4-v1-0-df713aad1531@tailscale.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 11 Oct 2026 01:41:26 +0000 you wrote:
> I hit this by accident while working on something else: bulk TCP through
> GRE-over-FOU tunnels between some EC2 VMs crawled at about one segment per
> round trip, and turning GRO off on the receiving NIC made it go away. I'm
> not a kernel networking person, so I went to debug it with an LLM coding
> agent, and it found what's below.
>
> Please consider this series a bug report at best. Feel free to ignore it,
> or to fix it some other way if this isn't the right fix; I may well have
> this wrong. Empirically, though, patch 1 fixes the packet loss we were
> seeing, both on our VMs and in the reproducer in patch 2.
>
> [...]
Here is the summary with links:
- [net,1/2] gre: keep the UDP tunnel GSO type when completing GRO
https://git.kernel.org/netdev/net/c/718f364a20ec
- [net,2/2] selftests: net: add a test for GRO of GRE over FOU and GUE
https://git.kernel.org/netdev/net/c/d0eb9632fd98
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-10-17 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 1:41 [PATCH net 0/2] gre: merged GRE-over-FOU/GUE packets are dropped (bug report, possible fix) Brad Fitzpatrick via B4 Relay
2026-10-11 1:41 ` [PATCH net 1/2] gre: keep the UDP tunnel GSO type when completing GRO Brad Fitzpatrick via B4 Relay
2026-10-11 8:55 ` Eric Dumazet
2026-10-11 1:41 ` [PATCH net 2/2] selftests: net: add a test for GRO of GRE over FOU and GUE Brad Fitzpatrick via B4 Relay
2026-10-17 1:50 ` 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=179220180976.1055958.15695873779763495713.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=atenart@kernel.org \
--cc=bradfitz@tailscale.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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