netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>,
	netfilter-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	syzbot+5d8c5789c8cb076b2c25@syzkaller.appspotmail.com
Subject: Re: [PATCH nf] netfilter: nf_tables: make destruction work queue pernet
Date: Thu, 6 Mar 2025 03:50:30 +0100	[thread overview]
Message-ID: <20250306025030.GB23740@breakpoint.cc> (raw)
In-Reply-To: <Z8jLZv6asBnqrniC@calendula>

Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> >  	mutex_unlock(&nft_net->commit_mutex);
> > +
> > +	cancel_work_sync(&nft_net->destroy_work);
> 
> __nft_release_tables() is called in this nf_tables_exit_net()
> function, cancel_work_sync() needs to be called before it?

Yep, thanks.  Will fix in v2.

> > @@ -12029,10 +12036,8 @@ static void __exit nf_tables_module_exit(void)
> >  	unregister_netdevice_notifier(&nf_tables_flowtable_notifier);
> >  	nft_chain_filter_fini();
> >  	nft_chain_route_fini();
> > -	nf_tables_trans_destroy_flush_work();
> 
> My understanding is that this is not required anymore because of the
> new cancel_work_sync() in the exit_net() path?

Right, the flush now needs to be done in exit_net and it happens
as part of the cancel_work_sync call.


      reply	other threads:[~2025-03-06  2:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 11:55 [PATCH nf] netfilter: nf_tables: make destruction work queue pernet Florian Westphal
2025-03-05 22:08 ` Pablo Neira Ayuso
2025-03-06  2:50   ` 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=20250306025030.GB23740@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=syzbot+5d8c5789c8cb076b2c25@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).