| 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: Thu, 21 Aug 2014 18:25:55 +0200 From: Sam Ravnborg <sam@...nborg.org> To: Mathias Krause <minipli@...glemail.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Joe Perches <joe@...ches.com>, Rasmus Villemoes <linux@...musvillemoes.dk>, linux-kernel@...r.kernel.org Subject: Re: [PATCHv3 0/9] Mark literal strings in __init / __exit code On Thu, Aug 21, 2014 at 02:23:03PM +0200, Mathias Krause wrote: > This is v3 of the patch series initially posted here: > > https://lkml.org/lkml/2014/6/22/149 > > This series tries to address the problem of dangling strings of __init > functions after initialization, as well as __exit strings for code not > even included in the final kernel image. The code might get freed, but > the format strings are not, as they're in the wrong section. What potential are we looking at here? Anything less than a page in size would likely not matter as this is the granularity we look into. And the code needs to be built-in - which most drivers are not. So is it really worth it? The places that already moves the string to __init/__exit should maybe be droopped to avoid the complication. Sam -- 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