From: Florian Westphal <fw@strlen.de>
To: Vastargazing <vebohr@gmail.com>
Cc: pablo@netfilter.org, netfilter-devel@vger.kernel.org,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] selftests: netfilter: add nft_ct timeout destroy race test
Date: Wed, 22 Apr 2026 15:51:09 +0200 [thread overview]
Message-ID: <aejSTa7PcHkaOs4C@strlen.de> (raw)
In-Reply-To: <20260422131818.106417-2-vebohr@gmail.com>
Vastargazing <vebohr@gmail.com> wrote:
> new file mode 100644
This should say '755', else you get
# Warning: file nft_ct_timeout_concurrency.sh is not executable
I'm not sure we should add regression tests for regression tests sake.
Else we'll quickly accumulate thousands of such scripts and test
run time will explode.
A functional test for timeout policies would be much more useful.
We have a few of those in nftables.git but they ony check that
userspace and kernel parsing sides work.
prev parent reply other threads:[~2026-04-22 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 13:18 [PATCH 0/1] selftests: netfilter: add regression test for nft_ct timeout UAF Vastargazing
2026-04-22 13:18 ` [PATCH 1/1] selftests: netfilter: add nft_ct timeout destroy race test Vastargazing
2026-04-22 13:51 ` 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=aejSTa7PcHkaOs4C@strlen.de \
--to=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=shuah@kernel.org \
--cc=vebohr@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox