From: Florian Westphal <fw@strlen.de>
To: Giuseppe Scrivano <gscrivan@redhat.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC PATCH] netfilter: call synchronize_net only once from nf_register_net_hooks
Date: Wed, 22 Nov 2017 11:41:03 +0100 [thread overview]
Message-ID: <20171122104103.GE24866@breakpoint.cc> (raw)
In-Reply-To: <20171122104026.7592-1-gscrivan@redhat.com>
Giuseppe Scrivano <gscrivan@redhat.com> wrote:
> SELinux, if enabled, registers for each new network namespace 6
> netfilter hooks. Avoid to use synchronize_net for each new hook, but do
> it once after all the hooks are added. The net benefit on an SMP
> machine with two cores is that creating a new network namespace takes
> -40% of the original time.
>
> Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
> ---
> net/netfilter/core.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/net/netfilter/core.c b/net/netfilter/core.c
> index 52cd2901a097..beeb0b36f429 100644
> --- a/net/netfilter/core.c
> +++ b/net/netfilter/core.c
> @@ -252,7 +252,7 @@ static struct nf_hook_entries __rcu **nf_hook_entry_head(struct net *net, const
> return NULL;
> }
>
> -int nf_register_net_hook(struct net *net, const struct nf_hook_ops *reg)
> +static int __nf_register_net_hook(struct net *net, const struct nf_hook_ops *reg)
> {
> struct nf_hook_entries *p, *new_hooks;
> struct nf_hook_entries __rcu **pp;
> @@ -291,11 +291,19 @@ int nf_register_net_hook(struct net *net, const struct nf_hook_ops *reg)
> #ifdef HAVE_JUMP_LABEL
> static_key_slow_inc(&nf_hooks_needed[reg->pf][reg->hooknum]);
> #endif
> - synchronize_net();
> BUG_ON(p == new_hooks);
> kvfree(p);
This adds use after free?
next prev parent reply other threads:[~2017-11-22 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 10:40 [RFC PATCH] netfilter: call synchronize_net only once from nf_register_net_hooks Giuseppe Scrivano
2017-11-22 10:41 ` Florian Westphal [this message]
2017-11-22 11:06 ` Florian Westphal
2017-11-22 11:10 ` Florian Westphal
2017-11-22 11:25 ` Giuseppe Scrivano
2017-11-22 11:56 ` Florian Westphal
2017-11-22 14:30 ` Giuseppe Scrivano
2017-11-22 14:54 ` Florian Westphal
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=20171122104103.GE24866@breakpoint.cc \
--to=fw@strlen.de \
--cc=gscrivan@redhat.com \
--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).