public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Jakub Kicinski <kuba@kernel.org>,
	edumazet@google.com, netfilter-devel@vger.kernel.org,
	pabeni@redhat.com, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [net,2/2] netfilter: nf_tables: unconditionally bump set->nelems before insertion
Date: Thu, 26 Feb 2026 17:28:01 +0100	[thread overview]
Message-ID: <aaB0kaSgbnSgVFBE@chamomile> (raw)
In-Reply-To: <aaACGbUnAyQiV3ut@strlen.de>

On Thu, Feb 26, 2026 at 09:19:37AM +0100, Florian Westphal wrote:
> Jakub Kicinski <kuba@kernel.org> wrote:
> > This is an AI-generated review of your patch. The human sending this
> > email says "Is this legit?"
> 
> Looks legit to me.
> 
> > For local reproduction steps see https://netdev-ai.bots.linux.dev/ai-local.html
> > ---
> > netfilter: nf_tables: unconditionally bump set->nelems before insertion
> > 
> > This commit addresses a race condition where a new element gets published
> > then removed without waiting for the RCU grace period when the set is full.
> > The fix moves the nelems increment before insertion and adds cleanup logic
> > using the abort path to safely unwind the set.
> > 
> > > diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
> > > index 0c5a4855b97d..834736237b09 100644
> > > --- a/net/netfilter/nf_tables_api.c
> > > +++ b/net/netfilter/nf_tables_api.c
> > > @@ -7171,6 +7171,7 @@ static int nft_add_set_elem(struct nft_ctx *ctx, struct nft_set *set,
> > >  	struct nft_data_desc desc;
> > >  	enum nft_registers dreg;
> > >  	struct nft_trans *trans;
> > > +	bool set_full = false;
> > >  	u64 expiration;
> > >  	u64 timeout;
> > >  	int err, i;
> > > @@ -7462,10 +7463,18 @@ static int nft_add_set_elem(struct nft_ctx *ctx, struct nft_set *set,
> > >  	if (err < 0)
> > >  		goto err_elem_free;
> > >
> > > +	if (!(flags & NFT_SET_ELEM_CATCHALL)) {
> > > +		unsigned int max = nft_set_maxsize(set), nelems;
> > > +
> > > +		nelems = atomic_inc_return(&set->nelems);
> > > +		if (nelems > max)
> > > +			set_full = true;
> > > +	}
> > > +
> > >  	trans = nft_trans_elem_alloc(ctx, NFT_MSG_NEWSETELEM, set);
> > >  	if (trans == NULL) {
> > >  		err = -ENOMEM;
> > > -		goto err_elem_free;
> > > +		goto err_set_size;
> > >  	}
> > >
> > >  	ext->genmask = nft_genmask_cur(ctx->net);
> > > @@ -7517,7 +7526,7 @@ static int nft_add_set_elem(struct nft_ctx *ctx, struct nft_set *set,
> > >
> > >  					ue->priv = elem_priv;
> > >  					nft_trans_commit_list_add_elem(ctx->net, trans);
> > > -					goto err_elem_free;
> > > +					goto err_set_size;
> > >  				}
> > >  			}
> > >  		}
> > > @@ -7535,23 +7544,16 @@ static int nft_add_set_elem(struct nft_ctx *ctx, struct nft_set *set,
> > >  		goto err_element_clash;
> > >  	}
> > >
> > > -	if (!(flags & NFT_SET_ELEM_CATCHALL)) {
> > > -		unsigned int max = nft_set_maxsize(set);
> > > -
> > > -		if (!atomic_add_unless(&set->nelems, 1, max)) {
> > > -			err = -ENFILE;
> > > -			goto err_set_full;
> > > -		}
> > > -	}
> > > -
> > >  	nft_trans_container_elem(trans)->elems[0].priv = elem.priv;
> > >  	nft_trans_commit_list_add_elem(ctx->net, trans);
> > > -	return 0;
> > >
> > > -err_set_full:
> > > -	nft_setelem_remove(ctx->net, set, elem.priv);
> > > +	return set_full ? -ENFILE : 0;
> > > +
> > >  err_element_clash:
> > >  	kfree(trans);
> > > +err_set_size:
> > > +	if (!(flags & NFT_SET_ELEM_CATCHALL) && !set_full)
> > > +		atomic_dec(&set->nelems);
> > 
> > Does this properly handle the element update path when the set is full?
> 
> Pablo, why does that check !set_full?  The increment is unconditional,
> so why is the decrement asymmetric?
> 
> err_set_size:
>         if (!(flags & NFT_SET_ELEM_CATCHALL))
>                 atomic_dec(&set->nelems);
> 
> ?

I think so, this is a leftover from initial patches that where still
using conditional atomic_add_unless().

I'm preparing a re-spin.

  reply	other threads:[~2026-02-26 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 13:06 [PATCH net 0/2] netfilter updates for net Florian Westphal
2026-02-25 13:06 ` [PATCH net 1/2] netfilter: nf_conntrack_h323: fix OOB read in decode_choice() Florian Westphal
2026-02-26  9:10   ` Florian Westphal
2026-02-26 11:47     ` Paolo Abeni
2026-02-26 14:14       ` Florian Westphal
2026-02-26 11:48     ` Paolo Abeni
2026-02-26 14:00   ` patchwork-bot+netdevbpf
2026-02-25 13:06 ` [PATCH net 2/2] netfilter: nf_tables: unconditionally bump set->nelems before insertion Florian Westphal
2026-02-26  3:56   ` [net,2/2] " Jakub Kicinski
2026-02-26  8:19     ` Florian Westphal
2026-02-26 16:28       ` Pablo Neira Ayuso [this message]
2026-02-26 17:19         ` Paolo Abeni

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=aaB0kaSgbnSgVFBE@chamomile \
    --to=pablo@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.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