[PATCH 0/4][RFC] netns: sysfs: add a netns suffix to net devicesysfs entries

From: Benjamin Thery
Date: Wed Oct 22 2008 - 11:23:32 EST

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.

Reminder for those not aware of the netns/sysfs issue:

With network namespaces, the kernel must be able to support net devices
with the same name in different network namespaces: the most obvious
example being the loopback device, which exists in every namespace.
The remaining place where this doesn't work yet is sysfs.

In the last 12 months, Eric Biederman proposed different approaches
to support this and sent several patchsets to implement what he calls
"sysfs tagged directories". But unfortunately, there is still no
agreement on the patchset and its implementation.

See last round of comments there:

So, currently testing network namespaces on a mainline kernel is a
pain and involves either to disable sysfs completely (argh) or to find
and manually apply Eric's latest patchset (was in gregkh's tree for a
short time, but unfortunately it was dumped out a few a weeks ago).

This patchset explores an alternative suggested by Serge Hallyn
to *temporarily* fix this issue. It introduces the modifications
needed to register in sysfs, the network devices belonging to child
network namespaces with a suffix appended to their name to avoid
potential conflicts.


Network devices from the initial network namespace are untouched.
Their representation in sysfs (/sys/class/net/, ...) is unchanged.

Network devices from sub-network namespaces appear in sysfs
with a name that looks like this: device_name@netns_id
eg: lo@3, eth0@4e

See last patch of the series for the details.

Then, if needed in the child network namespace, we can filter
/sys/class/net contents with, for example:

* mount -t tmpfs /sys/class/net
* and manually link the right devices from /sys/devices/virtual/net
(ln -s ../../devices/virtual/net/lo@1 lo)

This is less elegant than Eric's approach, but is quite simple and
doesn't touch sysfs core code.

This patch applies on top of net-next-2.6.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/