linux-kernel - [PATCH locking 0/4] locktorture and memory-barriers.txt updates

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: <20160426172041.GA4539@linux.vnet.ibm.com>
Date:	Tue, 26 Apr 2016 10:20:41 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	mingo@...nel.org, corbet@....net, peterz@...radead.org,
	linux-doc@...r.kernel.org, dhowells@...hat.com,
	will.deacon@....com, dave@...olabs.net
Subject: [PATCH locking 0/4] locktorture and memory-barriers.txt updates

Hello!

This series contains a few memory-barriers.txt updates and a locktorture
cleanup:

1.	Add a disclaimer to memory-barrier.txt, courtesy of
	Peter Zijlstra.

2.	Explicitly state the purpose of memory-barrier.txt, courtesy
	of David Howells.

3.	Explicitly state that ACQUIRE applies to loads and that
	RELEASE applies to stores, courtesy of Will Deacon.

4.	Simplify torture_runnable computation in locktorture, replacing
	a multiline #ifdef with an IS_ENABLED() that fits into an
	existing line.

							Thanx, Paul

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

 Documentation/memory-barriers.txt |   39 +++++++++++++++++++++++++++++++++++++-
 kernel/locking/locktorture.c      |    7 ------
 2 files changed, 39 insertions(+), 7 deletions(-)