From: Florian Westphal <fw@strlen.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net] selftests: netfilter: nft_queue.sh: increase udp_gro_ct subtest timeout
Date: Tue, 24 Feb 2026 16:09:17 +0100 [thread overview]
Message-ID: <aZ2_Hc3oQgukfVDy@strlen.de> (raw)
In-Reply-To: <20260224065921.0d4f5cdc@kernel.org>
Jakub Kicinski <kuba@kernel.org> wrote:
> Thanks for looking into it! Unfortunately we saw the problem again with
> this patch applied:
> https://netdev-ctrl.bots.linux.dev/logs/vmksft/nf-dbg/results/531881/3-nft-queue-sh/stdout
>
> Looks like it repros once every 25 runs for us:
> https://netdev.bots.linux.dev/contest.html?executor=vmksft-nf-dbg&test=nft-queue-sh
Yes, I already saw that it did not help, I can't explain this so far. I
restarted a long test run (1000 runs) with '--cpus 4' on my laptop, I
hope it triggers this time :-/
You can mark this patch as deferred or changes requested, I will
hopefully be able to send a v2 that gets rid of this problem.
prev parent reply other threads:[~2026-02-24 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 19:00 [PATCH net] selftests: netfilter: nft_queue.sh: increase udp_gro_ct subtest timeout Florian Westphal
2026-02-24 14:59 ` Jakub Kicinski
2026-02-24 15:09 ` 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=aZ2_Hc3oQgukfVDy@strlen.de \
--to=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@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