summaryrefslogtreecommitdiff
path: root/net/unix
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2007-11-19 22:27:40 -0800
committerDavid S. Miller <davem@davemloft.net>2008-01-28 14:54:26 -0800
commit4b3da706bbe4613d2fe4df8df4d965954ea98964 (patch)
treeaba584cfbf5a70cfbc95ea87faebdbec5ea2c64a /net/unix
parent97c53cacf00d1f5aa04adabfebcc806ca8b22b10 (diff)
downloadlinux-3.10-4b3da706bbe4613d2fe4df8df4d965954ea98964.tar.gz
linux-3.10-4b3da706bbe4613d2fe4df8df4d965954ea98964.tar.bz2
linux-3.10-4b3da706bbe4613d2fe4df8df4d965954ea98964.zip
[NET]: Make the netlink methods in rtnetlink handle multiple network namespaces
After the previous prep work this just consists of removing checks limiting the code to work in the initial network namespace, and updating rtmsg_ifinfo so we can generate events for devices in something other then the initial network namespace. Referring to network other network devices like the IFLA_LINK and IFLA_MASTER attributes do, gets interesting if those network devices happen to be in other network namespaces. Currently ifindex numbers are allocated globally so I have taken the path of least resistance and not still report the information even though the devices they are talking about are invisible. If applications start getting confused or when ifindex numbers become local to the network namespace we may need to do something different in the future. Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Denis V. Lunev <den@openz.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/unix')
0 files changed, 0 insertions, 0 deletions