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  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]
Date:	Sat, 18 Oct 2014 13:50:18 -0700
From:	Linus Torvalds <>
To:	Davidlohr Bueso <>
Cc:	Catalin Marinas <>,
	Linux Kernel Mailing List <>,
	Matteo Franchin <>,
	Darren Hart <>,
	Thomas Gleixner <>,
	Peter Zijlstra <>,
	Ingo Molnar <>,
	"Paul E. McKenney" <>,
	Mike Galbraith <>
Subject: Re: [PATCH] futex: Ensure get_futex_key_refs() always implies a barrier

On Sat, Oct 18, 2014 at 12:58 PM, Davidlohr Bueso <> wrote:
> And [get/put]_futex_keys() shouldn't even be called for private futexes.
> The following patch had some very minor testing on a 60 core box last
> night, but passes both Darren's and perf's tests. So I *think* this is
> right, but lack of sleep and I overall just don't trust them futexes!

Hmm. I don't see the advantage of making the code more complex in
order to avoid the functions that are no-ops for the !fshared case?

IOW, as far as I can tell, this patch doesn't actually really *change*
anything. Am I missing something?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists