netdev - Re: [PATCH net,v2 0/7] Netfilter fixes for net

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250717062338.18ed7f69@kernel.org>
Date: Thu, 17 Jul 2025 06:23:38 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Florian Westphal <fw@...len.de>
Cc: Paolo Abeni <pabeni@...hat.com>, Pablo Neira Ayuso
 <pablo@...filter.org>, netfilter-devel@...r.kernel.org,
 davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 horms@...nel.org
Subject: Re: [PATCH net,v2 0/7] Netfilter fixes for net

On Thu, 17 Jul 2025 15:01:53 +0200 Florian Westphal wrote:
> Paolo Abeni <pabeni@...hat.com> wrote:
> > The first run of the newly introduced conntrack_clash.sh test failed on
> > nipa:
> > 
> > # timeout set to 1800
> > # selftests: net/netfilter: conntrack_clash.sh
> > # got 128 of 128 replies
> > # timed out while waiting for reply from thread
> > # got 127 of 128 replies
> > # FAIL: did not receive expected number of replies for 10.0.1.99:22111
> > # FAIL: clash resolution test for 10.0.1.99:22111 on attempt 2
> > # got 128 of 128 replies
> > # timed out while waiting for reply from thread
> > # got 0 of 128 replies
> > # FAIL: did not receive expected number of replies for 127.0.0.1:9001
> > # FAIL: clash resolution test for 127.0.0.1:9001 on attempt 2
> > # SKIP: Clash resolution did not trigger
> > not ok 1 selftests: net/netfilter: conntrack_clash.sh # exit=1
> > I think the above should not block the PR, but please have a look.  
> 
> No idea whats happening, I get 100/100 ok :-/
> 
> I'll send a revert or $ksft_skip for now if I can't figure it out.

Oh, I see this disembodied thread now, sorry.

No need to send the skip, we can ignore the case when ingesting results.