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

[Jakub Kicinski <kuba@kernel.org>]

On Thu, 17 Jul 2025 06:23:38 -0700 Jakub Kicinski wrote:
> On Thu, 17 Jul 2025 15:01:53 +0200 Florian Westphal wrote:
> > Paolo Abeni <pabeni@redhat.com> wrote:  
> > > # 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.

FWIW

# nft --version
nftables v1.1.3 (Commodore Bullmoose #4)

nftables# git log -1 --format=reference 
610089f2 (cache: Tolerate object deserialization failures, 2025-05-16)