From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: [PATCH 05/11] netfilter: nft_flow_offload: wait for garbage collector to run after cleanup
Date: Wed, 7 Feb 2018 18:42:23 +0100 [thread overview]
Message-ID: <20180207174229.4098-6-pablo@netfilter.org> (raw)
In-Reply-To: <20180207174229.4098-1-pablo@netfilter.org>
If netdevice goes down, then flowtable entries are scheduled to be
removed. Wait for garbage collector to have a chance to run so it can
delete them from the hashtable.
The flush call might sleep, so hold the nfnl mutex from
nft_flow_table_iterate() instead of rcu read side lock. The use of the
nfnl mutex is also implicitly fixing races between updates via nfnetlink
and netdevice event.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
net/netfilter/nf_tables_api.c | 8 ++++----
net/netfilter/nft_flow_offload.c | 1 +
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
index 0791813a1e7d..07dd1fac78a8 100644
--- a/net/netfilter/nf_tables_api.c
+++ b/net/netfilter/nf_tables_api.c
@@ -5006,13 +5006,13 @@ void nft_flow_table_iterate(struct net *net,
struct nft_flowtable *flowtable;
const struct nft_table *table;
- rcu_read_lock();
- list_for_each_entry_rcu(table, &net->nft.tables, list) {
- list_for_each_entry_rcu(flowtable, &table->flowtables, list) {
+ nfnl_lock(NFNL_SUBSYS_NFTABLES);
+ list_for_each_entry(table, &net->nft.tables, list) {
+ list_for_each_entry(flowtable, &table->flowtables, list) {
iter(&flowtable->data, data);
}
}
- rcu_read_unlock();
+ nfnl_unlock(NFNL_SUBSYS_NFTABLES);
}
EXPORT_SYMBOL_GPL(nft_flow_table_iterate);
diff --git a/net/netfilter/nft_flow_offload.c b/net/netfilter/nft_flow_offload.c
index 4503b8dcf9c0..1739ff8ca21f 100644
--- a/net/netfilter/nft_flow_offload.c
+++ b/net/netfilter/nft_flow_offload.c
@@ -208,6 +208,7 @@ static void nft_flow_offload_iterate_cleanup(struct nf_flowtable *flowtable,
void *data)
{
nf_flow_table_iterate(flowtable, flow_offload_iterate_cleanup, data);
+ flush_delayed_work(&flowtable->gc_work);
}
static int flow_offload_netdev_event(struct notifier_block *this,
--
2.11.0
next prev parent reply other threads:[~2018-02-07 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 17:42 [PATCH 00/11] Netfilter fixes for net Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 01/11] netfilter: x_tables: make allocation less aggressive Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 02/11] netfilter: ipv6: nf_defrag: Kill frag queue on RFC2460 failure Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 03/11] netfilter: flowtable infrastructure depends on NETFILTER_INGRESS Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 04/11] netfilter: xt_cgroup: initialize info->priv in cgroup_mt_check_v1() Pablo Neira Ayuso
2018-02-07 17:42 ` Pablo Neira Ayuso [this message]
2018-02-07 17:42 ` [PATCH 06/11] netfilter: nft_flow_offload: no need to flush entries on module removal Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 07/11] netfilter: xt_RATEEST: acquire xt_rateest_mutex for hash insert Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 08/11] netfilter: nft_flow_offload: move flowtable cleanup routines to nf_flow_table Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 09/11] netfilter: nf_tables: fix flowtable free Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 10/11] netfilter: remove useless prototype Pablo Neira Ayuso
2018-02-07 17:42 ` [PATCH 11/11] netfilter: nf_flow_offload: fix use-after-free and a resource leak Pablo Neira Ayuso
2018-02-07 18:56 ` [PATCH 00/11] Netfilter fixes for net David Miller
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=20180207174229.4098-6-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).