| 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, 25 Jun 2014 10:34:25 +0200 From: Mathias Krause <minipli@...glemail.com> To: Joe Perches <joe@...ches.com> Cc: Rasmus Villemoes <linux@...musvillemoes.dk>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Steven Rostedt <rostedt@...dmis.org>, "Rafael J. Wysocki" <rjw@...ysocki.net>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com> Subject: Re: [RFC PATCH 0/3] Mark literal strings in __init / __exit code On 25 June 2014 09:48, Joe Perches <joe@...ches.com> wrote: > On Wed, 2014-06-25 at 09:35 +0200, Rasmus Villemoes wrote: >> Speaking of dangling pointers: A similar disaster would happen if some >> code containing pi_* calls gets copy-pasted to some non-__init >> function. > > This is my biggest issue with adding these new, > somewhat obscure macros. modpost will handle these cases. >> Could checkpatch learn to warn about calling these functions >> from the wrong context? > > It's not possible. checkpatch works on patch chunks. > Any patch chunk may not contain the function attributes. checkpatch.pl -f might detect them, though :/ Thanks, Mathias -- 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