From: David Miller <davem@davemloft.net>
To: den@openvz.org
Cc: containers@lists.osdl.org, netdev@vger.kernel.org,
ebiederm@xmission.com, dlezcano@fr.ibm.com
Subject: Re: [PATCH 2.6.25 3/6] net: Make the netlink methods in rtnetlink handle multiple network namespaces
Date: Mon, 19 Nov 2007 22:33:47 -0800 (PST) [thread overview]
Message-ID: <20071119.223347.64509613.davem@davemloft.net> (raw)
In-Reply-To: <20071115155836.GA25458@iris.sw.ru>
From: "Denis V. Lunev" <den@openvz.org>
Date: Thu, 15 Nov 2007 18:58:36 +0300
> From: Eric W. Biederman <ebiederm@xmission.com>
>
> After the previous prep work this just consists of removing checks
> limiting the code to work in the initial network namespace, and
> updating rtmsg_ifinfo so we can generate events for devices in
> something other then the initial network namespace.
>
> Referring to network other network devices like the IFLA_LINK
> and IFLA_MASTER attributes do, gets interesting if those network
> devices happen to be in other network namespaces. Currently
> ifindex numbers are allocated globally so I have taken the path
> of least resistance and not still report the information even
> though the devices they are talking about are invisible.
>
> If applications start getting confused or when ifindex
> numbers become local to the network namespace we may need
> to do something different in the future.
>
> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
> Signed-off-by: Denis V. Lunev <den@openz.org>
Applied, thanks.
prev parent reply other threads:[~2007-11-20 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 15:58 [PATCH 2.6.25 3/6] net: Make the netlink methods in rtnetlink handle multiple network namespaces Denis V. Lunev
2007-11-20 6:33 ` 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=20071119.223347.64509613.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=containers@lists.osdl.org \
--cc=den@openvz.org \
--cc=dlezcano@fr.ibm.com \
--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).