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  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:	Mon, 10 Sep 2007 14:36:26 -0700 (PDT)
From:	Christoph Lameter <>
To:	"Paul E. McKenney" <>
cc:	Segher Boessenkool <>,
	Paul Mackerras <>,,, Stefan Richter <>,
	Satyam Sharma <>,
	Linux Kernel Mailing List <>,
	David Miller <>,
	Ilpo Järvinen <>,,,,
	Netdev <>,,,
	Andrew Morton <>,,, Chris Snook <>,
	Herbert Xu <>,
	Linus Torvalds <>,,
Subject: Re: [PATCH 0/24] make atomic_read() behave consistently across all

On Mon, 10 Sep 2007, Paul E. McKenney wrote:

> The one exception to this being the case where process-level code is
> communicating to an interrupt handler running on that same CPU -- on
> all CPUs that I am aware of, a given CPU always sees its own writes
> in order.

Yes but that is due to the code path effectively continuing in the 
interrupt handler. The cpu makes sure that op codes being executed always 
see memory in a consistent way. The basic ordering problem with out of 
order writes is therefore coming from other processors concurrently 
executing code and holding variables in registers that are modified 
elsewhere. The only solution that I know of are one or the other form of 
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