| 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: Tue, 18 Feb 2014 19:52:16 +0100 From: Andi Kleen <andi@...stfloor.org> To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> Cc: Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org, sam@...nborg.org, x86@...nel.org, linux-kbuild@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>, rusty@...tcorp.com.au Subject: Re: [PATCH 19/20] lto, module: Warn about modules that are not fully LTOed On Tue, Feb 18, 2014 at 09:50:39AM -0500, Konrad Rzeszutek Wilk wrote: > On Tue, Feb 18, 2014 at 03:28:57PM +0100, Andi Kleen wrote: > > From: Andi Kleen <ak@...ux.intel.com> > > > > When __gnu_lto_* is present that means that the module hasn't run with > > LTO yet. > > The title says 'warn' but this is not a warning just information. > > Can you actually build modules against the kernel with different compiler > options? I thought it would complain when trying to load about some > form of mismatch? Sure it has worked forever (I think the only reason we still check compiler versions was some ancient long obsolete ABI problem) LTO is also fully ABI compatible. Hmm I think this patch can be actually removed now because I default to slim LTO, and with that it wouldn't even load if this happens. I'll remove it. -Andi -- 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