From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: "Eric W. Biederman" <ebiederm@aristanetworks.com>,
Pavel Emelyanov <xemul@openvz.org>, Thomas Graf <tgraf@suug.ch>
Subject: [PATCH 1/3] net: make namespace iteration possible under RCU
Date: Tue, 07 Jul 2009 14:08:37 +0200 [thread overview]
Message-ID: <20090707121422.343021507@sipsolutions.net> (raw)
In-Reply-To: 20090707120835.953398074@sipsolutions.net
[-- Attachment #1: 029-netns-rcu.patch --]
[-- Type: text/plain, Size: 2344 bytes --]
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 | 14 +++++++++++---
2 files changed, 14 insertions(+), 3 deletions(-)
--- wireless-testing.orig/include/net/net_namespace.h 2009-07-07 04:14:39.000000000 +0200
+++ wireless-testing/include/net/net_namespace.h 2009-07-07 12:17:17.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-07-07 03:43:35.000000000 +0200
+++ wireless-testing/net/core/net_namespace.c 2009-07-07 12:18:19.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>
@@ -127,7 +128,7 @@ static struct net *net_create(void)
rv = setup_net(net);
if (rv == 0) {
rtnl_lock();
- list_add_tail(&net->list, &net_namespace_list);
+ list_add_tail_rcu(&net->list, &net_namespace_list);
rtnl_unlock();
}
mutex_unlock(&net_mutex);
@@ -156,9 +157,16 @@ 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();
+ /*
+ * Another CPU might be rcu-iterating the list, wait for it.
+ * This needs to be before calling the exit() notifiers, so
+ * the rcu_barrier() below isn't sufficient alone.
+ */
+ synchronize_rcu();
+
/* Run all of the network namespace exit methods */
list_for_each_entry_reverse(ops, &pernet_list, list) {
if (ops->exit)
@@ -219,7 +227,7 @@ static int __init net_ns_init(void)
panic("Could not setup the initial network namespace");
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);
--
next prev parent reply other threads:[~2009-07-07 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 12:08 [PATCH 0/3] network namespaces for generic netlink Johannes Berg
2009-07-07 12:08 ` Johannes Berg [this message]
2009-07-07 12:08 ` [PATCH 2/3] genetlink: make netns aware Johannes Berg
2009-07-07 21:24 ` Johannes Berg
2009-07-07 12:08 ` [PATCH 3/3] net: move and export get_net_ns_by_pid 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=20090707121422.343021507@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ebiederm@aristanetworks.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=xemul@openvz.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).