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: Sat, 10 May 2008 14:37:44 +0200 From: Andi Kleen <andi@...stfloor.org> To: Vegard Nossum <vegard.nossum@...il.com> Cc: Bart Van Assche <bart.vanassche@...il.com>, John Reiser <jreiser@...Wagon.com>, Pekka Enberg <penberg@...helsinki.fi>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Christoph Lameter <clameter@....com>, Daniel Walker <dwalker@...sta.com>, Andi Kleen <andi@...stfloor.org>, Randy Dunlap <randy.dunlap@...cle.com>, Josh Aune <luken@...er.org>, Pekka Paalanen <pq@....fi> Subject: Re: [ANNOUNCE] kmemcheck v7 > - kmemcheck can only warn for dynamic memory, whereas kmemcheck I > believe will also work for local variables, static variables, etc. I don't think that's true. valgrind can only detect uninitialized local variables in one special case (first use of the stack region). But as soon as you reuse stack which is pretty common it won't be able to detect the next uninitialized use in a stack frame. Luckily the compilers do a reasonable job at detecting them at build time. And static/global variables are never uninitialized in C. -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