From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 09 Oct 2009 17:22:23 +0000 Subject: Re: PATCH: Network Device Naming mechanism and policy Message-Id: <20091009172223.GA4649@kroah.com> List-Id: References: <20091009140000.GA18765@mock.linuxdev.us.dell.com> <20091009163613.GA3414@kroah.com> <20091009171724.GA11004@auslistsprd01.us.dell.com> In-Reply-To: <20091009171724.GA11004@auslistsprd01.us.dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Matt Domsch Cc: Narendra K , netdev@vger.kernel.org, linux-hotplug@vger.kernel.org, jordan_hargrave@dell.com On Fri, Oct 09, 2009 at 12:17:24PM -0500, Matt Domsch wrote: > > uevents aren't namespaced. Presumably that means /dev can't be > polyinstantiated. Therefore, all devnodes in /dev/netdev/* will be > visible to all processes, where 'ifconfig' and friends would only show > device names in the processes namespace. This doesn't mean the app > can _do_ anything (it's the same as if it tried to act on a device > using an ifindex for a device not in its namespace), but yes, the fact > that such a device exists will be exposed. That's the problem that the sysfs namespace patches were trying to address. Now I'm not saying it is a valid thing to try to work with this kind of crazy, I was just wondering how it would work out. Looks like it doesn't :) thanks, greg k-h