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: <20070916.170700.116353255.davem@davemloft.net> Date: Sun, 16 Sep 2007 17:07:00 -0700 (PDT) From: David Miller <davem@...emloft.net> To: ebiederm@...ssion.com Cc: shemminger@...ux-foundation.org, xemul@...nvz.org, netdev@...r.kernel.org, containers@...ts.osdl.org, devel@...nvz.org, dlezcano@...ibm.com Subject: Re: [PATCH][NETNS] Use list_for_each_entry_continue_reverse in setup_net From: ebiederm@...ssion.com (Eric W. Biederman) Date: Sun, 16 Sep 2007 18:06:00 -0600 > I did that audit when I replied to Stephen the first time and I just > redid it to verify myself. We are calling functions that can fail > from the init function (kmalloc in the most common). So the > init function can fail. > > So short of adding a bunch of BUG_ON's to the kernel to trap those > failure cases we can't remove the backwards list walk. Especially > since I can initiate this code path as root by calling > "clone(CLONE_NEWNET...)". I just noticed that posting and thanks for reiterating. - 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