aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@maxwell.aristanetworks.com>2008-11-08 01:54:20 -0500
committerDavid S. Miller <davem@davemloft.net>2008-11-08 01:54:20 -0500
commit505d4f73dda9e20d59da05008f1f5eb432613e71 (patch)
treea30032d6474ce1d8dea1853c1907f4c3bdd8a19c /include
parent5d6d480908300a0c0b3be8b58567dfcef62c83a5 (diff)
net: Guaranetee the proper ordering of the loopback device. v2
I was recently hunting a bug that occurred in network namespace cleanup. In looking at the code it became apparrent that we have and will continue to have cases where if we have anything going on in a network namespace there will be assumptions that the loopback device is present. Things like sending igmp unsubscribe messages when we bring down network devices invokes the routing code which assumes that at least the loopback driver is present. Therefore to avoid magic initcall ordering hackery that is hard to follow and hard to get right insert a call to register the loopback device directly from net_dev_init(). This guarantes that the loopback device is the first device registered and the last network device to go away. But do it carefully so we register the loopback device after we clear dev_boot_phase. Signed-off-by: Eric W. Biederman <ebiederm@maxwell.aristanetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include')
-rw-r--r--include/linux/netdevice.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index f1b0dbe58464..12d7f4469dc9 100644
--- a/include/linux/netdevice.h
+++ b/include/linux/netdevice.h
@@ -1766,6 +1766,7 @@ static inline int skb_bond_should_drop(struct sk_buff *skb)
1766 return 0; 1766 return 0;
1767} 1767}
1768 1768
1769extern struct pernet_operations __net_initdata loopback_net_ops;
1769#endif /* __KERNEL__ */ 1770#endif /* __KERNEL__ */
1770 1771
1771#endif /* _LINUX_DEV_H */ 1772#endif /* _LINUX_DEV_H */