"Serge E. Hallyn" <[EMAIL PROTECTED]> writes: > Quoting Eric W. Biederman ([EMAIL PROTECTED]): >> Benjamin Thery <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED], they'll see lo. > Userspace in a container can either umount /sys completely, or do
The well-known user space tools don't use /sys at all. Modern network tools use rtnetlink (ip) old network tools use /proc/net. Very few things actually use /sys and for those things [EMAIL PROTECTED] or [EMAIL PROTECTED] are completely useless except for implementing a FUSE mock up of sysfs. But you don't need anything in sysfs to do that as all of the interesting information is available through /proc/net or rtnetlink. > > mount -t tmpfs none /sys/class/net > mount --bind /sys/devices/virtual/net/[EMAIL PROTECTED] > /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? No. ABI decisions are almost certainly irreversible. If we need an immediate hack please see the patch I sent in follow up. We can achieve everything Ben is doing by simply keeping virtual devices out of the kobject tree. Keeping them from showing up in sysfs. Eric _______________________________________________ Containers mailing list [EMAIL PROTECTED] https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list [email protected] https://openvz.org/mailman/listinfo/devel
