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, 25 Oct 2007 09:15:50 +0200 From: Andi Kleen <ak@...e.de> To: Nick Piggin <nickpiggin@...oo.com.au> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: Is gcc thread-unsafe? On Thursday 25 October 2007 05:24, Nick Piggin wrote: > Basically, what the gcc developers are saying is that gcc is > free to load and store to any memory location, so long as it > behaves as if the instructions were executed in sequence. This case is clearly a bug, a very likely code pessimization. I guess it wasn't intentional, just an optimization that is useful for local register values doing too much. > I guess that dynamically allocated memory and computed pointers > are more difficult for gcc to do anything unsafe with, because > it is harder to tell if a given function has deallocated the > memory. Often accesses happen without function calls inbetween. Also I think newer gcc (not 3.x) can determine if a pointer "escapes" or not so that might not protect against it. > Any thoughts? We don't have much choice: If such a case is found it has to be marked volatile or that particular compiler version be unsupported. It might be useful to come up with some kind of assembler pattern matcher to check if any such code is generated for the kernel and try it with different compiler versions. -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