[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081022203045.GA4633@us.ibm.com>
Date: Wed, 22 Oct 2008 15:30:45 -0500
From: "Serge E. Hallyn" <serue@...ibm.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Benjamin Thery <benjamin.thery@...l.net>,
netdev <netdev@...r.kernel.org>,
Dave Miller <davem@...emloft.net>,
Greg Kroah-Hartman <gregkh@...e.de>,
Al Viro <viro@....linux.org.uk>,
Daniel Lezcano <dlezcano@...ibm.com>,
linux-kernel@...r.kernel.org, Tejun Heo <htejun@...il.com>,
Denis Lunev <den@...nvz.org>,
Linux Containers <containers@...ts.linux-foundation.org>
Subject: Re: [PATCH 0/4][RFC] netns: sysfs: add a netns suffix to net
device sysfs entries
Quoting Eric W. Biederman (ebiederm@...ssion.com):
> Benjamin Thery <benjamin.thery@...l.net> writes:
>
> > Support for network namespaces in mainline is pretty complete for
> > some time now, but there is still this issue with sysfs that prevents
> > more people to use it easily.
>
> Ben your patchset is completely inappropriate.
>
> Temporarily adding elements to the ABI that we intend to remove
> is not a proper solution to this problem.
>
> That user space visible ida you add is a namespace identifier that breaks
> nested containers and migration. It is very very very wrong.
I disagree (not surprising :) completely. The well-known userspace
tools (ifconfig, ip, etc) will not see the lo@1, they'll see lo.
Userspace in a container can either umount /sys completely, or do
mount -t tmpfs none /sys/class/net
mount --bind /sys/devices/virtual/net/lo@1 /sys/class/net/lo
if they really want to, in which case only their view
of /sys/devices/virtual/net would be different.
Eric, would you hate this less if it was under some
CONFIG_SYSFS_NETNS_HACK
config variable?
-serge
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists