From: Paolo Abeni <pabeni@redhat.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
edumazet@google.com, fw@strlen.de, horms@kernel.org
Subject: Re: [PATCH net,v2 0/7] Netfilter fixes for net
Date: Thu, 17 Jul 2025 14:38:10 +0200 [thread overview]
Message-ID: <33ce1182-00fa-4255-b51c-d4dc927071bc@redhat.com> (raw)
In-Reply-To: <20250717095808.41725-1-pablo@netfilter.org>
On 7/17/25 11:58 AM, Pablo Neira Ayuso wrote:
> v2: Include conntrack fix in cover letter.
>
> -o-
>
> Hi,
>
> The following batch contains Netfilter fixes for net:
>
> 1) Three patches to enhance conntrack selftests for resize and clash
> resolution, from Florian Westphal.
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.
Thanks,
Paolo
next prev parent reply other threads:[~2025-07-17 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 9:58 [PATCH net,v2 0/7] Netfilter fixes for net Pablo Neira Ayuso
2025-07-17 12:38 ` Paolo Abeni [this message]
2025-07-17 13:01 ` Florian Westphal
2025-07-17 13:23 ` Jakub Kicinski
2025-07-17 13:31 ` Jakub Kicinski
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=33ce1182-00fa-4255-b51c-d4dc927071bc@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).