| 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
| ||
|
Date: Wed, 18 Feb 2009 15:52:31 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Ivan Kokshaysky <ink@...assic.park.msu.ru> Cc: hch@...radead.org, rth@...ddle.net, viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org Subject: Re: [PATCH] alpha: binfmt_aout fix On Tue, 17 Feb 2009 14:40:56 +0300 Ivan Kokshaysky <ink@...assic.park.msu.ru> wrote: > On Tue, Feb 17, 2009 at 06:08:42AM -0500, Christoph Hellwig wrote: > > I think the proper fix for this is to make sure newly registered > > binfmts are added to the tail of the list, not the front. > > Yes, I was thinking about that. But then I need to make sure > that alpha binfmt_loader is registered first, which is not > possible at the moment as binfmts get registered at core_initcall > level. > If it's acceptable to change binfmts initcall level to, say, > fs_initcall, then changing list_add() to list_add_tail() would > certainly work fine here. > It would make sense to register the core, default handlers first and to permit arch-specific handlers to then override (or to front-end) the core handlers. But that sounds a bit risky for 2.6.29. Is this fix needed in 2.6.29? If so, perhaps we should merge version 1 as a temporary thing. But if so, please let's not do the temporary-thing-which-hangs-around-forever thing? -- 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