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: Sun, 12 Aug 2007 11:11:25 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Segher Boessenkool <segher@...nel.crashing.org> cc: schwidefsky@...ibm.com, wjiang@...ilience.com, wensong@...ux-vs.org, heiko.carstens@...ibm.com, linux-kernel@...r.kernel.org, ak@...e.de, cfriesen@...tel.com, netdev@...r.kernel.org, horms@...ge.net.au, akpm@...ux-foundation.org, Chuck Ebbert <cebbert@...hat.com>, davem@...emloft.net, zlynx@....org, Chris Snook <csnook@...hat.com> Subject: Re: [PATCH] make atomic_t volatile on all architectures On Sun, 12 Aug 2007, Segher Boessenkool wrote: > > Yeah. Compiler errors are more annoying though I dare say ;-) Actually, compile-time errors are fine, and easy to work around. *Much* more annoying is when gcc actively generates subtly bad code. We've had use-after-free issues due to incorrect gcc liveness calculations etc, and inline asm has beeen one of the more common causes - exactly because the kernel is one of the few users (along with glibc) that uses it at all. Now *those* are hard to find - the code works most of the time, but the compiler has inserted a really subtle race condition into the code (deallocated a local stack entry before last use). We had that with our semaphore code at some point. Linus - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists