linux-kernel - Re: Linux 2.6.32-rc1

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.01.0909291410440.6996@localhost.localdomain>
Date:	Tue, 29 Sep 2009 14:17:58 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Eric Dumazet <eric.dumazet@...il.com>
cc:	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	John Stultz <johnstul@...ibm.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: Linux 2.6.32-rc1

On Tue, 29 Sep 2009, Eric Dumazet wrote:
> 
> Checking this commit, I believe problem comes from cmpxchg(), which doesnt 
> handle 64 bit on X86_32 (no compilation error, and  null operation :( )

Wow. That's broken. Very nasty silent failure.

> 1) Use cmpxchg64()

Clearly better than what we have now, although cmpxchg64 does result is 
some really disgusting code. We will use a bare CMPXCHG64 only if you 
compile for PAE right now - so even if you tell Kconfig that you want to 
compile for a modern CPU, we won't be doing that whole cmpxchg64b thing 
directly, we'll inline some really disgusting code.

So we really need to fix that up before it would be acceptable to use 
cmpxchg64(). 

And regardless, we should fix the silent cmpxchg failure, even if it's 
just a link-time failure or something. 64-bit things in the kernel used to 
be rare and special, but they aren't any more.

Ingo, Peter, comments?

		Linus
--
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/