From: Florian Westphal <fw@strlen.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [TEST] nf_nat_edemux.sh flakes
Date: Thu, 2 Oct 2025 08:41:39 +0200 [thread overview]
Message-ID: <aN4eozX50WVSf_LK@strlen.de> (raw)
In-Reply-To: <20250927090709.0b3cd783@kernel.org>
Jakub Kicinski <kuba@kernel.org> wrote:
> > Jakub Kicinski <kuba@kernel.org> wrote:
> > > nf_nat_edemux.sh started flaking in NIPA quite a bit more around a week ago.
> > >
> > Weird, I don't recall changes in nat engine.
> > I'll have a look sometime next week.
Looks like its not a regression but just tripping due to
"1 second is long enough" not being safe anymore on debug builds.
I'll rewrite this to have it query conntrack for relevant entries
instead of failing in case socat needed more than 1s to complete.
> While you're looking, nft-fib-sh also flakes occasionally:
> https://netdev.bots.linux.dev/contest.html?pass=0&executor=vmksft-nf-dbg&test=nft-fib-sh
D'oh. I think this is just because I did not RTFM.
"ping -c 1" can send more than 1 packet when combined with -w
(deadline), so its failing occasionally because the packet counter
is *higher* than expected.
prev parent reply other threads:[~2025-10-02 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 23:33 [TEST] nf_nat_edemux.sh flakes Jakub Kicinski
2025-09-27 10:47 ` Florian Westphal
2025-09-27 16:07 ` Jakub Kicinski
2025-10-02 6:41 ` Florian Westphal [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=aN4eozX50WVSf_LK@strlen.de \
--to=fw@strlen.de \
--cc=kuba@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).