From: Paolo Abeni <pabeni@redhat.com>
To: Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Shuah Khan <shuah@kernel.org>,
Maciej enczykowski <maze@google.com>,
Lina Wang <lina.wang@mediatek.com>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net] selftests: net: add missing required classifier
Date: Thu, 25 Jan 2024 12:38:26 +0100 [thread overview]
Message-ID: <ecf42dd37e90fec22edd16f64b55189a24147b21.camel@redhat.com> (raw)
In-Reply-To: <CANn89iKqShowy=xMi2KwthYB6gz9X5n9kcqwh_5-JBJ3-jnK+g@mail.gmail.com>
On Thu, 2024-01-25 at 09:48 +0100, Eric Dumazet wrote:
> On Thu, Jan 25, 2024 at 9:23 AM Paolo Abeni <pabeni@redhat.com> wrote:
> >
> > the udpgro_fraglist self-test uses the BPF classifiers, but the
> > current net self-test configuration does not include it, causing
> > CI failures:
> >
> > # selftests: net: udpgro_frglist.sh
> > # ipv6
> > # tcp - over veth touching data
> > # -l 4 -6 -D 2001:db8::1 -t rx -4 -t
> > # Error: TC classifier not found.
> > # We have an error talking to the kernel
> > # Error: TC classifier not found.
> > # We have an error talking to the kernel
> >
> > Add the missing knob.
> >
> > Fixes: edae34a3ed92 ("selftests net: add UDP GRO fraglist + bpf self-tests")
> > Signed-off-by: Paolo Abeni <pabeni@redhat.com>
>
> FYI, while looking at the gro test, I found that using strace was
> making it failing as well.
It looks like the gro.sh (large) tests send the to-be-aggregate
segments individually and relay on the gro flush timeout being large
enough to fit all the relevant write operations. I suspect/hope
something alike:
---
diff --git a/tools/testing/selftests/net/setup_veth.sh b/tools/testing/selftests/net/setup_veth.sh
index a9a1759e035c..1f78a87f6f37 100644
--- a/tools/testing/selftests/net/setup_veth.sh
+++ b/tools/testing/selftests/net/setup_veth.sh
@@ -11,7 +11,7 @@ setup_veth_ns() {
local -r ns_mac="$4"
[[ -e /var/run/netns/"${ns_name}" ]] || ip netns add "${ns_name}"
- echo 100000 > "/sys/class/net/${ns_dev}/gro_flush_timeout"
+ echo 1000000 > "/sys/class/net/${ns_dev}/gro_flush_timeout"
ip link set dev "${ns_dev}" netns "${ns_name}" mtu 65535
ip -netns "${ns_name}" link set dev "${ns_dev}" up
---
should solve the sporadic issues.
> Not sure about this one...
All the udpgro* test should write a single UDP GSO packet and let the
veth segmenting it, hopefully slowing down either ends should not
impact them - but I did not check yet!
Perhaps even the gro.sh tests could be modified alike?
Cheers,
Paolo
next prev parent reply other threads:[~2024-01-25 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 8:22 [PATCH net] selftests: net: add missing required classifier Paolo Abeni
2024-01-25 8:33 ` Maciej Żenczykowski
2024-01-25 8:48 ` Eric Dumazet
2024-01-25 11:38 ` Paolo Abeni [this message]
2024-01-25 14:10 ` Eric Dumazet
2024-01-25 16:40 ` Paolo Abeni
2024-01-25 16:42 ` Eric Dumazet
2024-01-26 22:10 ` Jakub Kicinski
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=ecf42dd37e90fec22edd16f64b55189a24147b21.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lina.wang@mediatek.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).