From: Phil Sutter <phil@nwl.cc>
To: Qingfang Deng <qingfang.deng@linux.dev>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: flowtable: check namespace before iterating flows
Date: Wed, 9 Sep 2026 13:16:16 +0200 [thread overview]
Message-ID: <aqFAALdUODUjUMo0@orbyte.nwl.cc> (raw)
In-Reply-To: <20260909081705.1512600-1-qingfang.deng@linux.dev>
Hi,
On Wed, Sep 09, 2026 at 04:17:04PM +0800, Qingfang Deng wrote:
> nf_flow_table_cleanup() walks every registered flow table, checking the
> network namespace for each flow in nf_flow_table_do_cleanup(). As a
> result, tables in other namespaces are still iterated and their cleanup
> work is flushed.
>
> Compare the flow table's namespace with the device's namespace in
> nf_flow_table_cleanup() and skip nonmatching tables. This avoids
> unnecessary iteration and work flushing, and leaves the per-flow cleanup
> callback to check only the interface index.
>
> Signed-off-by: Qingfang Deng <qingfang.deng@linux.dev>
> ---
> net/netfilter/nf_flow_table_core.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/net/netfilter/nf_flow_table_core.c b/net/netfilter/nf_flow_table_core.c
> index 03241d4bfd5e..52cca7a8f141 100644
> --- a/net/netfilter/nf_flow_table_core.c
> +++ b/net/netfilter/nf_flow_table_core.c
> @@ -730,14 +730,9 @@ static void nf_flow_table_do_cleanup(struct nf_flowtable *flow_table,
> {
> struct net_device *dev = data;
>
> - if (!dev) {
> - flow_offload_teardown(flow);
> - return;
> - }
> -
> - if (net_eq(nf_ct_net(flow->ct), dev_net(dev)) &&
> - (flow->tuplehash[0].tuple.iifidx == dev->ifindex ||
> - flow->tuplehash[1].tuple.iifidx == dev->ifindex))
> + if (!dev ||
> + flow->tuplehash[0].tuple.iifidx == dev->ifindex ||
> + flow->tuplehash[1].tuple.iifidx == dev->ifindex)
> flow_offload_teardown(flow);
> }
>
> @@ -754,8 +749,10 @@ void nf_flow_table_cleanup(struct net_device *dev)
> struct nf_flowtable *flowtable;
>
> mutex_lock(&flowtable_lock);
> - list_for_each_entry(flowtable, &flowtables, list)
> - nf_flow_table_gc_cleanup(flowtable, dev);
> + list_for_each_entry(flowtable, &flowtables, list) {
> + if (net_eq(read_pnet(&flowtable->net), dev_net(dev)))
> + nf_flow_table_gc_cleanup(flowtable, dev);
> + }
A second caller of nf_flow_table_gc_cleanup is
nf_flow_table_indr_cleanup in net/netfilter/nf_flow_table_offload.c. Is
the net_eq-check needed there as well? If not, could you please update
the patch description with a statement explaining why?
Thanks, Phil
> mutex_unlock(&flowtable_lock);
> }
> EXPORT_SYMBOL_GPL(nf_flow_table_cleanup);
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-09-09 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 8:17 [PATCH nf-next] netfilter: flowtable: check namespace before iterating flows Qingfang Deng
2026-09-09 11:16 ` Phil Sutter [this message]
2026-09-09 14:18 ` Qingfang Deng
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=aqFAALdUODUjUMo0@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=qingfang.deng@linux.dev \
/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.