From: Jiri Pirko <jpirko@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Netdev <netdev@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@aristanetworks.com>
Subject: Re: [PATCH] net: make namespace iteration possible under RCU
Date: Thu, 18 Jun 2009 13:45:16 +0200 [thread overview]
Message-ID: <20090618114516.GA6107@psychotron.englab.brq.redhat.com> (raw)
In-Reply-To: <1245323303.31588.86.camel@johannes.local>
Thu, Jun 18, 2009 at 01:08:23PM CEST, johannes@sipsolutions.net wrote:
>All we need to take care of is using proper RCU list
>add/del primitives and inserting a synchronize_rcu()
>at one place to make sure the exit notifiers are run
>after everybody has stopped iterating the list.
>
>Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
>---
> include/net/net_namespace.h | 3 +++
> net/core/net_namespace.c | 10 +++++++---
> 2 files changed, 10 insertions(+), 3 deletions(-)
>
>--- wireless-testing.orig/include/net/net_namespace.h 2009-06-18 01:36:26.000000000 +0200
>+++ wireless-testing/include/net/net_namespace.h 2009-06-18 02:17:14.000000000 +0200
>@@ -211,6 +211,9 @@ static inline struct net *read_pnet(stru
> #define for_each_net(VAR) \
> list_for_each_entry(VAR, &net_namespace_list, list)
>
>+#define for_each_net_rcu(VAR) \
>+ list_for_each_entry_rcu(VAR, &net_namespace_list, list)
>+
> #ifdef CONFIG_NET_NS
> #define __net_init
> #define __net_exit
>--- wireless-testing.orig/net/core/net_namespace.c 2009-06-18 01:36:39.000000000 +0200
>+++ wireless-testing/net/core/net_namespace.c 2009-06-18 02:03:06.000000000 +0200
>@@ -6,6 +6,7 @@
> #include <linux/delay.h>
> #include <linux/sched.h>
> #include <linux/idr.h>
>+#include <linux/rculist.h>
> #include <net/net_namespace.h>
> #include <net/netns/generic.h>
>
>@@ -134,7 +135,7 @@ struct net *copy_net_ns(unsigned long fl
> err = setup_net(new_net);
> if (!err) {
> rtnl_lock();
>- list_add_tail(&new_net->list, &net_namespace_list);
>+ list_add_tail_rcu(&new_net->list, &net_namespace_list);
> rtnl_unlock();
> }
> mutex_unlock(&net_mutex);
>@@ -163,9 +164,12 @@ static void cleanup_net(struct work_stru
>
> /* Don't let anyone else find us. */
> rtnl_lock();
>- list_del(&net->list);
>+ list_del_rcu(&net->list);
> rtnl_unlock();
>
>+ /* if somebody is rcu-iterating the list, wait */
>+ synchronize_rcu();
IMHO you do not need to call synchronize_rcu() here since rcu_barrier() is
called later just before net_free(net). Seems redundant.
Jirka
>+
> /* Run all of the network namespace exit methods */
> list_for_each_entry_reverse(ops, &pernet_list, list) {
> if (ops->exit)
>@@ -227,7 +231,7 @@ static int __init net_ns_init(void)
> err = setup_net(&init_net);
>
> rtnl_lock();
>- list_add_tail(&init_net.list, &net_namespace_list);
>+ list_add_tail_rcu(&init_net.list, &net_namespace_list);
> rtnl_unlock();
>
> mutex_unlock(&net_mutex);
>
>
>--
>To unsubscribe from this list: send the line "unsubscribe netdev" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-18 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 11:08 [PATCH] net: make namespace iteration possible under RCU Johannes Berg
2009-06-18 11:45 ` Jiri Pirko [this message]
2009-06-18 12:15 ` Johannes Berg
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=20090618114516.GA6107@psychotron.englab.brq.redhat.com \
--to=jpirko@redhat.com \
--cc=ebiederm@aristanetworks.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@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