linux-kernel - [PATCH 0/3] tools/memory-model: Add SRCU support

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]

Date:   Thu, 15 Nov 2018 11:19:24 -0500 (EST)
From:   Alan Stern <stern@...land.harvard.edu>
To:     "Paul E. McKenney" <paulmck@...ux.ibm.com>
cc:     LKMM Maintainers -- Akira Yokosawa <akiyks@...il.com>,
        Andrea Parri <andrea.parri@...rulasolutions.com>,
        Boqun Feng <boqun.feng@...il.com>,
        Daniel Lustig <dlustig@...dia.com>,
        David Howells <dhowells@...hat.com>,
        Jade Alglave <j.alglave@....ac.uk>,
        Luc Maranget <luc.maranget@...ia.fr>,
        Nicholas Piggin <npiggin@...il.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Will Deacon <will.deacon@....com>,
        Kernel development list <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/3] tools/memory-model: Add SRCU support

Paul and other LKMM maintainers:

The following series of patches adds support for SRCU to the Linux
Kernel Memory Model.  That is, it adds the srcu_read_lock(),
srcu_read_unlock(), and synchronize_srcu() primitives to the model.

	Patch 1/3 does some renaming of the RCU parts of the
	memory model's existing CAT code, to help distinguish them
	from the upcoming SRCU parts.

	Patch 2/3 refactors the definitions of some RCU relations
	in the CAT code, in a way that the SRCU portions will need.

	Patch 3/3 actually adds the SRCU support.

This new code requires herd7 version 7.51+4(dev) or later (now 
available in the herdtools7 github repository) to run.  Thanks to Luc 
for making the necessary changes to support SRCU.

The code does not check that the index argument passed to 
srcu_read_unlock() is the same as the value returned by the 
corresponding srcu_read_lock() call.  This is deemed to be a semantic 
issue, not directly relevant to the memory model.

Alan