From: Matthieu Baerts <matttbe@kernel.org>
To: Bryon Fryer <bryon@fryer.io>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
horms@kernel.org, jasowangio@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
pabeni@redhat.com, shuah@kernel.org
Subject: Re: [PATCH net 2/2] selftests: net: check UDP tunnel GRO virtio offsets
Date: Fri, 20 Nov 2026 15:50:48 +0100 [thread overview]
Message-ID: <be78bd95-cb61-4e50-9452-93e567d174a8@kernel.org> (raw)
In-Reply-To: <20261112030708.1915665-3-bryon@fryer.io>
Hello,
On 12/11/2026 04:07, Bryon Fryer wrote:
> Feed ordinary Geneve/TCP packets through a NAPI TAP and bridge into a
> virtio-header TAP. Require a multi-segment GRO aggregate and compare its
> exported transport and checksum offsets with parsed wire headers. Include
> a GRO-off packet-integrity control. No output or no merge is not a pass.
I *think* this series is causing the veth.sh selftest to flake:
https://netdev.bots.linux.dev/contest.html?executor=vmksft-net-dbg&test=veth-sh
Logs:
https://netdev-ctrl.bots.linux.dev/logs/vmksft/net/results/918887/55-veth-sh/
https://netdev-ctrl.bots.linux.dev/logs/vmksft/net/results/918887/55-veth-sh-retry/
Maybe because the new tun_vnet_gro test leaves a tunnel socket behind?
Could you please check the whole net selftests on your side? (or your
new test, then veth.sh)
I suggest dropping the series for the moment to see if it improves the
situation on the CI side, there are some comments on the patches anyway.
pw-bot: cr
Cheers,
Matt
prev parent reply other threads:[~2026-11-20 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 3:07 [PATCH net 0/2] udp: preserve outer transport header after tunnel GRO Bryon Fryer
2026-11-12 3:07 ` [PATCH net 1/2] udp: restore " Bryon Fryer
2026-11-16 13:50 ` netdev-bot+sashiko
2026-11-19 23:20 ` Jakub Kicinski
2026-11-12 3:07 ` [PATCH net 2/2] selftests: net: check UDP tunnel GRO virtio offsets Bryon Fryer
2026-11-16 13:50 ` netdev-bot+sashiko
2026-11-20 14:50 ` Matthieu Baerts [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=be78bd95-cb61-4e50-9452-93e567d174a8@kernel.org \
--to=matttbe@kernel.org \
--cc=bryon@fryer.io \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jasowangio@gmail.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.