| 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: <b6fcc0a0712190215g58de1ad9m53aee165fecaa278@mail.gmail.com> Date: Wed, 19 Dec 2007 13:15:39 +0300 From: "Alexey Dobriyan" <adobriyan@...il.com> To: "David Chinner" <dgc@....com> Cc: lkml <linux-kernel@...r.kernel.org> Subject: Re: [patch, rfc] mm.h, security.h, key.h and preventing namespace poisoning On 12/19/07, David Chinner <dgc@....com> wrote: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7cd94146cd504016315608e297219f9fb7b1413b > > included security.h in mm.h and that is how I'm seeing the namespace > poisoning coming from key.h when !CONFIG_KEY. > > Including security.h in mm.h means much wider includes for pretty > much the entire kernel, and it opens up namespace issues like this > that never previously existed. ACK, removing sched.h from mm.h was quite painful and security.h added it back unconditionally. As result, standalone mm.h inclusion goes from ~9K to ~16K of code after preprocessing which is quite unpleasant. > --- a/include/linux/mm.h > +++ b/include/linux/mm.h > @@ -12,7 +12,6 @@ > #include <linux/prio_tree.h> > #include <linux/debug_locks.h> > #include <linux/mm_types.h> > -#include <linux/security.h> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists