- 16 Apr, 2008 40 commits
-
-
Pavel Emelyanov authored
Calls to ip6_tnl_lookup were stubbed with init_net - give them a proper one. Signed-off-by:
Pavel Emelyanov <xemul@openvz.org> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Pavel Emelyanov authored
Hashes and fallback device used in them will be per-net. Signed-off-by:
-
Pavel Emelyanov authored
Signed-off-by:
-
Pavel Emelyanov authored
This makes sit-generated traffic enter the namespace. Signed-off-by:
-
Pavel Emelyanov authored
Set proper net and mark a new device as NETNS_LOCAL before registering. Signed-off-by:
-
Pavel Emelyanov authored
I.e. replace init_net stubs in ip_route_output_key() calls. Signed-off-by:
-
Pavel Emelyanov authored
Just move all the hashes on the sit_net structure and patch the rest of the code appropriately. Signed-off-by:
-
Pavel Emelyanov authored
Allocate and register one in sit_init_net, use sitn->fb_tunnel_dev over the code and unregister one in sit_exit_net. Signed-off-by:
-
Pavel Emelyanov authored
Replace introduced in the previous patch init_net stubs with the proper net pointer. Signed-off-by:
-
Pavel Emelyanov authored
... to make them prepared for future hashes and fallback device move on the struct sit_net. Signed-off-by:
-
Pavel Emelyanov authored
Signed-off-by:
-
Pavel Emelyanov authored
This one was also disabled by default for sanity. Signed-off-by:
-
Pavel Emelyanov authored
I.e. set the proper net and mark as NETNS_LOCAL. Signed-off-by:
-
Pavel Emelyanov authored
As for the IPIP tunnel, there are some ip_route_output_key() calls in there that require a proper net so give one to them. And a proper net for the __get_dev_by_index hanging around. Signed-off-by:
-
Pavel Emelyanov authored
Very similar to what was done for the IPIP code. Signed-off-by:
-
Pavel Emelyanov authored
Everything is prepared for this change now. Create on in init callback, use it over the code and destroy on net exit. Signed-off-by:
-
Pavel Emelyanov authored
This is the part#2 of the patch #2 - get the proper net for these functions. This change in a separate patch in order not to get lost in a large previous patch. Signed-off-by:
-
Pavel Emelyanov authored
The fallback device and hashes are to become per-net, but many code doesn't have anything to get the struct net pointer from. So pass the proper net there with an extra argument. Signed-off-by:
-
Pavel Emelyanov authored
Signed-off-by:
-
Pavel Emelyanov authored
This one was disabled by default for sanity. Signed-off-by:
-
Pavel Emelyanov authored
Set the proper net before calling register_netdev and disable the tunnel device netns changing. Signed-off-by:
-
Pavel Emelyanov authored
There are some ip_route_output_key() calls in there that require a proper net so give one to them. Besides - give a proper net to a single __get_dev_by_index call in ipip_tunnel_bind_dev(). Signed-off-by:
-
Pavel Emelyanov authored
Either net or ipip_net already exists in all the required places, so just use one. Besides, tune net_init and net_exit calls to respectively initialize the hashes and destroy devices. Signed-off-by:
-
Pavel Emelyanov authored
This is the part#2 of the previous patch - get the proper net for these functions. I make it in a separate patch, so that this change does not get lost in a large previous patch. Signed-off-by:
-
Pavel Emelyanov authored
The hashes of tunnels will be per-net too, so prepare all the functions that uses them for this change by adding an argument. Use init_net temporarily in places, where the net does not exist explicitly yet. Signed-off-by:
-
Pavel Emelyanov authored
Create on in ipip_init_net(), use it all over the code (the proper place to get the net from already exists) and destroy in ipip_net_exit(). Signed-off-by:
-
Pavel Emelyanov authored
Signed-off-by:
-
Pavel Emelyanov authored
When van device is moved to another namespace proc files, related to this device, should also change one. Use the netdev REGISTER and UNREGISTER event handlers for this. Signed-off-by:
Patrick McHardy <kaber@trash.net> Signed-off-by:
-
Pavel Emelyanov authored
This one is similar to what I've done for TUN - set the proper net after device allocation and clean VLANs on net exit (use the rtnl_kill_links helper finally). Plus, drop explicit init_net usage and net != &init_net checks. Signed-off-by:
-
Pavel Emelyanov authored
This includes moving one on the struct vlan_net and s/vlan_name_type/vn->name_type/ over the code. Signed-off-by:
-
Pavel Emelyanov authored
It is created in a proper net, so make is show info, related to this particular net. Signed-off-by:
-
Pavel Emelyanov authored
The proc_vlan_dir and proc_vlan_conf migrate on the struct vlan_net and their creation uses the struct net. The devices' entries use the corresponding device's net. Signed-off-by:
-
Pavel Emelyanov authored
All proc files will be created in each net, so prepare them for this change now, not to mess it with real creation patch. The net != &init_net checks in them are for git-bisect sanity, but I will drop them soon. Signed-off-by:
-
Pavel Emelyanov authored
Unlike TUN, it is empty from the very beginning, and will be eventually populated later. Signed-off-by:
-
Pavel Emelyanov authored
Currently vlan group is searched using one key - the ifindex. We'll have to lookup the vlan_group by two keys - ifindex and net. Turning the vlan_group lookup key to struct net_device pointer will make this process easier. Besides, this will eliminate one more place in the networking, that assumes that indexes are unique in the kernel. Signed-off-by:
-
Pavel Emelyanov authored
This one is responsible for calling ->dellink on each net device found in net to help with vlan net_exit hook in the nearest future. Signed-off-by:
-
Pavel Emelyanov authored
Each potential list_del (happening from inside a ->dellink call) is followed by goto restart, so there's no need in _safe iteration. Signed-off-by:
-
Pavel Emelyanov authored
This is basically means that a net is set for a new device, but actually also involves two more steps: 1. mark the tun device as "local", i.e. do not allow for it to move across namespaces. This is done so, since tun device is most often associated to some file (and thus to some process) and moving the device alone is not valid while keeping the file and the process outside. The need in ability to move a detached persistent device is to be investigated later. 2. get the tun device's net when tun becomes attached and put one when it becomes detached. This is needed to handle the case when a task owning the tun dies, but a files lives for some more time - in this case we must not allow for net to be freed, since its exit hook will spoil that file's private data by unregistering the tun from under tun_chr_close. Signed-off-by:
-
Pavel Emelyanov authored
Remove the static tun_dev_list and replace its occurrences in driver with per-net one. It is used in two places - in tun_set_iff and tun_cleanup. In the first case it's legal to use current net_ns. In the cleanup call - move the loop, that unregisters all devices in net exit hook. Signed-off-by:
-
Pavel Emelyanov authored
This is the first step in making tuntap devices work in net namespaces. The structure mentioned is pointed by generic net pointer with tun_net_id id, and tun driver fills one on its load. It will contain only the tun devices list. So declare this structure and introduce net init and exit hooks. Signed-off-by:
-
