From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Aohan Mei <ljp1205831794@gmail.com>
Cc: netfilter-devel@vger.kernel.org, fw@strlen.de, phil@nwl.cc,
coreteam@netfilter.org, Aohan Mei <henrymei@tencent.com>,
TencentOS Corvus AI <corvus@tencent.com>,
stable@vger.kernel.org
Subject: Re: [PATCH nf v2] netfilter: nf_tables: skip expired catchall elements on insert and delete
Date: Fri, 11 Sep 2026 13:14:54 +0200 [thread overview]
Message-ID: <aqPirnuC6Rdebi8y@chamomile> (raw)
In-Reply-To: <20260910080324.2663491-1-ljp1205831794@gmail.com>
On Thu, Sep 10, 2026 at 04:03:19PM +0800, Aohan Mei wrote:
> From: Aohan Mei <henrymei@tencent.com>
>
> nft_setelem_catchall_insert() looks up duplicates with
> nft_set_elem_active() only, while nft_set_catchall_lookup() and the
> dump path additionally skip expired elements.
>
> Once a catchall element with a timeout expires, this predicate drift
> makes it invisible to userspace dumps, yet it still blocks
> re-insertion: with NLM_F_EXCL the request fails with -EEXIST, and
> without it the request reports success but silently inserts nothing.
> The stale entry only goes away when the (user-tunable) gc interval
> elapses, so the catchall rule may silently stop matching for an
> arbitrarily long time after its first expiration.
>
> The delete path shows the same drift: nft_setelem_catchall_deactivate()
> picks the first active-next entry in the catchall list, so with an
> expired entry still pending GC it retires the stale entry instead of
> the fresh one, and it deactivates an element that userspace no longer
> sees instead of failing with -ENOENT.
>
> Align both walks with the lookup and dump predicates: only an element
> that is active and not expired counts as a duplicate or delete
> candidate, using a single timestamp snapshot for the expiry checks.
>
> Reported-by: TencentOS Corvus AI <corvus@tencent.com>
> Cc: stable@vger.kernel.org
> Fixes: aaa31047a6d2 ("netfilter: nftables: add catch-all set element support")
> Assisted-by: CodeBuddy:Kimi-K3
> Signed-off-by: Aohan Mei <henrymei@tencent.com>
> ---
> v2: drop the is_dead check, it does not belong to this dedup walk;
> use __nft_set_elem_expired() with a single timestamp snapshot;
> also skip expired catchall elements in the delete path.
> v1: https://lore.kernel.org/netfilter-devel/REPLACE-WITH-V1-MESSAGE-ID
>
> net/netfilter/nf_tables_api.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
> index 765a92fa90d6..0f3449cca5d2 100644
> --- a/net/netfilter/nf_tables_api.c
> +++ b/net/netfilter/nf_tables_api.c
> @@ -6991,11 +6991,13 @@ static int nft_setelem_catchall_insert(const struct net *net,
> {
> struct nft_set_elem_catchall *catchall;
> u8 genmask = nft_genmask_next(net);
> + u64 tstamp = get_jiffies_64();
No, this does not work. This must use the tstamp that is stored in the
per-netns area.
> struct nft_set_ext *ext;
>
> list_for_each_entry(catchall, &set->catchall_list, list) {
> ext = nft_set_elem_ext(set, catchall->elem);
> - if (nft_set_elem_active(ext, genmask)) {
> + if (nft_set_elem_active(ext, genmask) &&
> + !__nft_set_elem_expired(ext, tstamp)) {
> *priv = catchall->elem;
> return -EEXIST;
> }
> @@ -7088,11 +7090,13 @@ static int nft_setelem_catchall_deactivate(const struct net *net,
> struct nft_set_elem *elem)
> {
> struct nft_set_elem_catchall *catchall;
> + u64 tstamp = get_jiffies_64();
> struct nft_set_ext *ext;
>
> list_for_each_entry(catchall, &set->catchall_list, list) {
> ext = nft_set_elem_ext(set, catchall->elem);
> - if (!nft_is_active_next(net, ext))
> + if (!nft_is_active_next(net, ext) ||
> + __nft_set_elem_expired(ext, tstamp))
> continue;
>
> kfree(elem->priv);
> --
> 2.43.7
>
prev parent reply other threads:[~2026-09-11 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 8:03 [PATCH nf v2] netfilter: nf_tables: skip expired catchall elements on insert and delete Aohan Mei
2026-09-11 11:14 ` Pablo Neira Ayuso [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=aqPirnuC6Rdebi8y@chamomile \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=corvus@tencent.com \
--cc=fw@strlen.de \
--cc=henrymei@tencent.com \
--cc=ljp1205831794@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=stable@vger.kernel.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 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.