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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 20 Oct 2009 11:26:25 +1030 From: Rusty Russell <rusty@...tcorp.com.au> To: Carmelo Amoroso <carmelo73@...il.com> Cc: Greg KH <greg@...ah.com>, Alan Jenkins <sourcejedi.lkml@...glemail.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "linux-kbuild" <linux-kbuild@...r.kernel.org> Subject: Re: Fast LKM symbol resolution with SysV ELH hash table On Tue, 20 Oct 2009 01:32:51 am Carmelo Amoroso wrote: > 2009/10/19 Greg KH <greg@...ah.com>: > > On Mon, Oct 19, 2009 at 01:45:20PM +0200, Carmelo Amoroso wrote: > >> Just a few other notes. The current implementation I did based on SysV > >> has a drawback that is not backward compatible, so you cannot use old > >> modules with a kernel with the option enabled due to changes on struct > >> kernel_symbol. > > > > Why would this be a problem? Whenever making a kernel config change, > > you should be able to rebuild everything, as lots of other configuration > > options are that way. > > This is not always true... there could be cases in which you cannot > recompile old modules > (e.g vendors that provide non GPL modules) And breaking them is a feature. I do not go out of my way to avoid breaking out-of-tree modules; it's certainly more important to have simple maintainable code. You guys figure out what the best speed/size tradeoff is, and send me the patch for review. Thanks! Rusty. -- 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