From: David Miller <davem@davemloft.net>
To: ebiederm@xmission.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: Support specifying the network namespace upon device creation.
Date: Sun, 08 Nov 2009 00:54:07 -0800 (PST) [thread overview]
Message-ID: <20091108.005407.91447800.davem@davemloft.net> (raw)
In-Reply-To: <m1eioggeux.fsf@fess.ebiederm.org>
From: ebiederm@xmission.com (Eric W. Biederman)
Date: Tue, 03 Nov 2009 01:03:02 -0800
>
> There is no good reason to not support userspace specifying the
> network namespace during device creation, and it makes it easier
> to create a network device and pass it to a child network namespace
> with a well known name.
>
> We have to be careful to ensure that the target network namespace
> for the new device exists through the life of the call. To keep
> that logic clear I have factored out the network namespace grabbing
> logic into rtnl_link_get_net.
>
> In addtion we need to continue to pass the source network namespace
> to the rtnl_link_ops.newlink method so that we can find the base
> device source network namespace.
>
> Signed-off-by: Eric W. Biederman <ebiederm@aristanetworks.com>
Applied to net-next-2.6, thanks!
prev parent reply other threads:[~2009-11-08 8:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 9:03 [PATCH] net: Support specifying the network namespace upon device creation Eric W. Biederman
2009-11-03 9:28 ` Eric Dumazet
2009-11-03 9:50 ` Eric W. Biederman
2009-11-03 9:56 ` Eric Dumazet
2009-11-03 10:06 ` Eric W. Biederman
2009-11-03 10:05 ` David Miller
2009-11-03 10:16 ` Eric Dumazet
2009-11-03 10:44 ` David Miller
2009-11-03 13:26 ` [PATCH net-next-2.6] net: cleanup include/net Eric Dumazet
2009-11-04 13:07 ` David Miller
2009-11-04 17:48 ` [PATCH net-next-2.6] net: cleanup include/linux Eric Dumazet
2009-11-04 17:51 ` David Miller
2009-11-03 10:32 ` [PATCH] net: Support specifying the network namespace upon device creation Eric W. Biederman
2009-11-08 8:54 ` David Miller [this message]
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=20091108.005407.91447800.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--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;
as well as URLs for NNTP newsgroup(s).