From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com
Subject: Re: [PATCH v2 net] selftests: netfilter: tone-down conntrack clash test
Date: Wed, 23 Jul 2025 01:30:12 +0000 [thread overview]
Message-ID: <175323421226.1016544.13216461197162224409.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250721223652.6956-1-fw@strlen.de>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Jul 2025 00:36:49 +0200 you wrote:
> The test is supposed to observe that the 'clash_resolve' stat counter
> incremented (i.e., the code path was covered).
> This check was incorrect, 'conntrack -S' needs to be called in the
> revevant namespace, not the initial netns.
>
> The clash resolution logic in conntrack is only exercised when multiple
> packets with the same udp quadruple race. Depending on kernel config,
> number of CPUs, scheduling policy etc. this might not trigger even
> after several retries. Thus the script eventually returns SKIP if the
> retry count is exceeded.
>
> [...]
Here is the summary with links:
- [v2,net] selftests: netfilter: tone-down conntrack clash test
https://git.kernel.org/netdev/net/c/dca56cc8b5c3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-07-23 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 22:36 [PATCH v2 net] selftests: netfilter: tone-down conntrack clash test Florian Westphal
2025-07-23 1:30 ` patchwork-bot+netdevbpf [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=175323421226.1016544.13216461197162224409.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.