linux-kernel - [PATCH tip/core/rcu 0/9] Stop using ACCESS

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-next>] [day] [month] [year] [list]

Message-ID: <20150316184155.GA24290@linux.vnet.ibm.com>
Date:	Mon, 16 Mar 2015 11:41:55 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	mingo@...nel.org, laijs@...fujitsu.com, dipankar@...ibm.com,
	akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
	josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
	rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
	dvhart@...ux.intel.com, fweisbec@...il.com, oleg@...hat.com,
	bobby.prani@...il.com
Subject: [PATCH tip/core/rcu 0/9] Stop using ACCESS_ONCE (for v4.2)

Hello!

This patch series converts from ACCESS_ONCE() to either READ_ONCE() or
WRITE_ONCE(), as appropriate.  This permits better code generation and
error checking, and is also more compatible with C11 directions.  Each
file is updated separately to simplify handling of git conflicts.

							Thanx, Paul

------------------------------------------------------------------------

 include/linux/rculist.h  |    6 -
 include/linux/rcupdate.h |   16 ++--
 kernel/rcu/rcutorture.c  |    2 
 kernel/rcu/srcu.c        |   10 +-
 kernel/rcu/tiny_plugin.h |   12 +--
 kernel/rcu/tree.c        |  184 +++++++++++++++++++++++------------------------
 kernel/rcu/tree_plugin.h |   93 +++++++++++------------
 kernel/rcu/tree_trace.c  |    6 -
 kernel/rcu/update.c      |   30 +++----
 9 files changed, 180 insertions(+), 179 deletions(-)

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