From: ebiederm@xmission.com (Eric W. Biederman)
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND nf] netfilter: avoid a race between nf_register_hook() and cleanup_net()
Date: Sat, 30 Jul 2016 08:24:37 -0500 [thread overview]
Message-ID: <87shurb6ne.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20160729161904.4F00BA0BD9@unicorn.suse.cz> (Michal Kubecek's message of "Fri, 29 Jul 2016 18:19:04 +0200 (CEST)")
Michal Kubecek <mkubecek@suse.cz> writes:
> There is a race condition between nf_{,un}register_hook() and
> cleanup_net() which can either trigger WARN check or cause a memory
> leak. The scenario is like this (2a and 2b are alternatives):
>
> 1. cleanup_net() removes one or more struct net from net_namespace_list
> 2a. nf_register_hook() adds per-netns hooks to all netns (but not those
> removed in step 1) and adds the hook to global nf_hook_list
> 2b. nf_unregister_hook() deletes per-netns hooks from all netns (but not
> those removed in step 1) and removes the hook from nf_hook_list
> 3. cleanup_net() calls pernet subsystem exit functions for netns being
> removed; one of them is netfilter_net_exit() which (among others)
> calls nf_unregister_net_hook() to unregister per-netns hooks for all
> hooks in nf_hook_list.
>
> In case (a), per-netns hooks are never added as the namespace was
> already invisible to for_each_net() in step 2a but an attempt to remove
> them in step 3 (the hook is already in nf_hook_list) triggers a WARN
> check in nf_unregister_net_hook() (no real harm done, however). In case
> (b), the per-netns hook is removed neither in step 2b (netns is already
> invisible to for_each_net()) nor in step 3 (the hook is already removed
> from nf_hook_list), causing a memory leak.
>
> Prevent the race by protecting the for_each_net() loop in
> nf_{,un}register_hook() (also) by net_mutex. There is already a
> precendens for this in rtnl_link_unregister() which addresses similar
> race.
So this analysis of a problem appears to be spot on.
Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com>
I really really want there to be a better way to do this, but it is
really not ok for a hook to continue it's life past
nf_unregister_net_hook as after that point the code may be removed
from the kernel (sigh).
Although keeping with the precedent and minimizing net_mutex
we could remove the WARN and keep nf_register_hook as it is.
But that sounds entirely too clever for a fix that will
probably be backported.
But that sounds entirely too clever for a fix that likely needs to be
backported.
Eric
> Fixes: 085db2c04557 ("netfilter: Per network namespace netfilter hooks.")
> Signed-off-by: Michal Kubecek <mkubecek@suse.cz>
> ---
> net/netfilter/core.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/net/netfilter/core.c b/net/netfilter/core.c
> index f39276d1c2d7..860978c9f82e 100644
> --- a/net/netfilter/core.c
> +++ b/net/netfilter/core.c
> @@ -193,6 +193,8 @@ int nf_register_hook(struct nf_hook_ops *reg)
> struct net *net, *last;
> int ret;
>
> + /* prevent race with cleanup_net() */
> + mutex_lock(&net_mutex);
> rtnl_lock();
> for_each_net(net) {
> ret = nf_register_net_hook(net, reg);
> @@ -201,6 +203,7 @@ int nf_register_hook(struct nf_hook_ops *reg)
> }
> list_add_tail(®->list, &nf_hook_list);
> rtnl_unlock();
> + mutex_unlock(&net_mutex);
>
> return 0;
> rollback:
> @@ -211,6 +214,7 @@ rollback:
> nf_unregister_net_hook(net, reg);
> }
> rtnl_unlock();
> + mutex_unlock(&net_mutex);
> return ret;
> }
> EXPORT_SYMBOL(nf_register_hook);
> @@ -219,11 +223,14 @@ void nf_unregister_hook(struct nf_hook_ops *reg)
> {
> struct net *net;
>
> + /* prevent race with cleanup_net() */
> + mutex_lock(&net_mutex);
> rtnl_lock();
> list_del(®->list);
> for_each_net(net)
> nf_unregister_net_hook(net, reg);
> rtnl_unlock();
> + mutex_unlock(&net_mutex);
> }
> EXPORT_SYMBOL(nf_unregister_hook);
next prev parent reply other threads:[~2016-07-30 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160729150033.E0250A0BD9@unicorn.suse.cz>
2016-07-29 16:19 ` [PATCH RESEND nf] netfilter: avoid a race between nf_register_hook() and cleanup_net() Michal Kubecek
2016-07-30 13:24 ` Eric W. Biederman [this message]
2016-08-01 12:34 ` Pablo Neira Ayuso
2016-08-26 17:31 ` Pablo Neira Ayuso
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=87shurb6ne.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=coreteam@netfilter.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).