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:	Tue, 21 Aug 2007 00:07:15 +0200
From:	Segher Boessenkool <>
To:	Chris Snook <>
Cc:	Christoph Lameter <>,
	Paul Mackerras <>,,
	Stefan Richter <>,,
	Satyam Sharma <>,
	Ilpo Jarvinen <>,
	Linux Kernel Mailing List <>,
	David Miller <>,
	"Paul E. McKenney" <>,,
	Netdev <>,,,,,
	Andrew Morton <>,,, Herbert Xu <>,
	Linus Torvalds <>,, Nick Piggin <>,
Subject: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

> Such code generally doesn't care precisely when it gets the update, 
> just that the update is atomic, and it doesn't loop forever.

Yes, it _does_ care that it gets the update _at all_, and preferably
as early as possible.

> Regardless, I'm convinced we just need to do it all in assembly.

So do you want "volatile asm" or "plain asm", for atomic_read()?
The asm version has two ways to go about it too...


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists