| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20081105.160047.174722021.davem@davemloft.net> Date: Wed, 05 Nov 2008 16:00:47 -0800 (PST) From: David Miller <davem@...emloft.net> To: ebiederm@...ssion.com Cc: dlezcano@...ibm.com, containers@...ts.osdl.org, den@...nvz.org, xemul@...nvz.org, netdev@...r.kernel.org Subject: Re: [PATCH 2/3] net: Guaranetee the proper ordering of the loopback device. From: ebiederm@...ssion.com (Eric W. Biederman) Date: Wed, 05 Nov 2008 15:25:39 -0800 > > 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. > > Signed-off-by: Eric W. Biederman <ebiederm@...ssion.com> Applied. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists