From: Jakub Kicinski <kuba@kernel.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: [TEST] conntrack_reverse_clash.sh flakes
Date: Sat, 6 Dec 2025 17:51:35 -0800 [thread overview]
Message-ID: <20251206175135.4a56591b@kernel.org> (raw)
Hi Florian!
We have a new faster NIPA setup, and now on non-debug builds we see
a few (4 a week to be exact) flakes in conntrack_reverse_clash.sh
List of flakes from the last 100 runs:
https://netdev.bots.linux.dev/contest.html?pass=0&test=conntrack-reverse-clash-sh
Example:
# selftests: net/netfilter: conntrack_reverse_clash.sh
# Port number changed, wanted 56789 got 5950
# ERROR: SNAT performed without any matching snat rule
# kill: sending signal to 16051 failed: No such process
not ok 1 selftests: net/netfilter: conntrack_reverse_clash.sh # exit=1
Looks like the test also occasionally flaked on the old setup ("remote"
column with "metal" instead of "virt") which is now shut down:
# selftests: net/netfilter: conntrack_reverse_clash.sh
# Port number changed, wanted 56789 got 54630
# Port number changed, wanted 56790 got 25814
# ERROR: SNAT performed without any matching snat rule
not ok 1 selftests: net/netfilter: conntrack_reverse_clash.sh # exit=1
so this isn't new, just more likely now..
Could you TAL when you have spare cycles? (BTW the new setup is owned
by netdev foundation so I can give you access if that helps).
next reply other threads:[~2025-12-07 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-07 1:51 Jakub Kicinski [this message]
2025-12-07 1:56 ` [TEST] conntrack_reverse_clash.sh flakes Jakub Kicinski
2025-12-07 10:40 ` Florian Westphal
2025-12-08 14:48 ` Florian Westphal
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=20251206175135.4a56591b@kernel.org \
--to=kuba@kernel.org \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.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).