Re: namespace support requires network modules to say "GPL"

Ben Greear [off-list ref] writes:

I have a module that has a collection of 2-port bridges.  These bridges are used
for emulation
purposes (somewhat similar to netem's feature set).  Each bridge is logically
independent
of the others.   To set up a bridge, I do something like:

echo add_my_bridge my_br1 eth0 eth1 > /proc/net/foo/config

Interesting.  Currently /proc/net is also per network namespace.
So normally I would say just call get_proc_net from inside your
proc handler and all would be well.

At another location in /proc (not under /proc/net) I would just do:
dev_get_by_name(current->nsproxy->net_ns, "ethX");

I would probably be paranoid and grab current->nsproxy->net_ns
when the file was opened and put it when the file was closed
just to ensure that if someone opened it and then passed
the file descriptor to someone else there were not any
weird little races.  But I don't expect that is a problem
in your case.

Personally, it seems useful for my module to be able to have eth0 in one
namespace
and eth1 in another, but I won't complain if they both have to be in the same
namespace
or even just in the default namespace due to GPL symbol issues.

It probably is easiest to move the devices after your module has
bridged them.

Eric