netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: nf_tables: use correct lock to protect gc_list
Date: Mon, 21 Aug 2023 15:13:11 +0200	[thread overview]
Message-ID: <ZONi53oXf8Agcvwh@calendula> (raw)
In-Reply-To: <20230821123332.34690-1-pablo@netfilter.org>

On Mon, Aug 21, 2023 at 02:33:32PM +0200, Pablo Neira Ayuso wrote:
> Use nf_tables_gc_list_lock spinlock, not nf_tables_destroy_list_lock to
> protect the destroy list.

For the record, this text should be instead:

  ... to protect the gc_list.

> Fixes: 5f68718b34a5 ("netfilter: nf_tables: GC transaction API to avoid race with control plane")
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
>  net/netfilter/nf_tables_api.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
> index a255456efae4..eb8b1167dced 100644
> --- a/net/netfilter/nf_tables_api.c
> +++ b/net/netfilter/nf_tables_api.c
> @@ -9456,9 +9456,9 @@ static void nft_trans_gc_work(struct work_struct *work)
>  	struct nft_trans_gc *trans, *next;
>  	LIST_HEAD(trans_gc_list);
>  
> -	spin_lock(&nf_tables_destroy_list_lock);
> +	spin_lock(&nf_tables_gc_list_lock);
>  	list_splice_init(&nf_tables_gc_list, &trans_gc_list);
> -	spin_unlock(&nf_tables_destroy_list_lock);
> +	spin_unlock(&nf_tables_gc_list_lock);
>  
>  	list_for_each_entry_safe(trans, next, &trans_gc_list, list) {
>  		list_del(&trans->list);
> -- 
> 2.30.2
> 

      reply	other threads:[~2023-08-21 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 12:33 [PATCH nf] netfilter: nf_tables: use correct lock to protect gc_list Pablo Neira Ayuso
2023-08-21 13:13 ` 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=ZONi53oXf8Agcvwh@calendula \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@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 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).