| 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: <m1ocwxi00a.fsf@fess.ebiederm.org> Date: Fri, 20 Feb 2009 07:47:01 -0800 From: ebiederm@...ssion.com (Eric W. Biederman) To: David Miller <davem@...emloft.net> Cc: Linux Containers <containers@...ts.osdl.org>, <netdev@...r.kernel.org>, Alexey Dobriyan <adobriyan@...il.com>, "Denis V. Lunev" <den@...nvz.org> Subject: [PATCH 0/3] Fix Network namespace shutdown take 2 6 months ago when I introduced net_alive I fixed the symptoms but I failed to properly fix network namespace shutdown. I realized this when I received a bug report on Tuesday about a failure in icmp_send caused by packets in the arp_gueue. It turns out that the net_alive check in netif_receive_skb is completely unnecessary and just masked the real problem. If we remove all network devices from a network namespace before we shutdown network subsystems and protocols then as designed we cannot have packets in flight causing problems. It turns out that the root cause of these problems is that the icmp code was calling register_pernet_device instead of register_pernet_subsys and so it's cleanup was happening much too early. The following patchset which should work against both 2.6.29-rcX and net-next fixes the registration problems and removes the unncessary net_alive check, making the code simpler and hopefully more comprehensible. Eric -- 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