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 0/3] network namespaces for generic netlink
Date: Tue, 07 Jul 2009 14:08:36 +0200 [thread overview]
Message-ID: <20090707120835.953398074@sipsolutions.net> (raw)
This is a repost of my earlier patches, now with
fixed semantics and locking. The first patch is
required to make RCU-iteration of the network
namespace list possible, which the second patch
requires.
The third patch is preparation for nl80211 netns
work, I'm happy to give that to John instead to
go via the wireless tree with the patch that will
make use of the now exported function, but it is
possible that other generic netlink users will
also require it once they being upgrading their
family to be netns aware.
johannes
next 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 Johannes Berg [this message]
2009-07-07 12:08 ` [PATCH 1/3] net: make namespace iteration possible under RCU Johannes Berg
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=20090707120835.953398074@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).