linux-kernel - Re: Compilers and RCU readers: Once more unto the breach!

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: <20150522131126.GF6776@linux.vnet.ibm.com>
Date:	Fri, 22 May 2015 06:11:26 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Richard Kenner <kenner@...i1.ultra.nyu.edu>
Cc:	mingo@...nel.org, akpm@...ux-foundation.org,
	c++std-parallel@...u.org, dhowells@...hat.com, gcc@....gnu.org,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	Mark.Batty@...cam.ac.uk, michaelw@...ibm.com,
	Peter.Sewell@...cam.ac.uk, peterz@...radead.org,
	Ramana.Radhakrishnan@....com, torvalds@...ux-foundation.org,
	will.deacon@....com
Subject: Re: Compilers and RCU readers: Once more unto the breach!

On Fri, May 22, 2015 at 06:43:32AM -0400, Richard Kenner wrote:
> > (Assuming it's a goal of this standard to be human parseable to more 
> > than a few dozen people on the planet.)
> 
> Unfortunately, that's rarely a goal of most standards. ;-)

My experience does match Richard's, sad to say.  There has been some
vigorous discussion in another thread involving undefined behavior and
value narrowing, which has resulted in some useful changes to Section 7.9.
The updated document is here:

	http://www2.rdrop.com/users/paulmck/RCU/consume.2015.05.22a.pdf

							Thanx, Paul

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