linux-kernel - [PATCH tip/core/rcu 0/4] SRCU changes for 3.8

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:	Tue, 30 Oct 2012 09:36:50 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	mingo@...e.hu, laijs@...fujitsu.com, dipankar@...ibm.com,
	akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
	josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
	peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
	dhowells@...hat.com, edumazet@...gle.com, darren@...art.com,
	fweisbec@...il.com, sbw@....edu, patches@...aro.org
Subject: [PATCH tip/core/rcu 0/4] SRCU changes for 3.8

Hello!

This patch series contains SRCU changes allowing srcu_structs to be
statically initialized.  The patches are as follows:

1.	Add Lai Jiangshan as author for srcu.c and srcu.h.
	(Courtesy Lia Jiangshan.)
2.	Export process_srcu() so that the initialization macro may
	be invoked anywhere.  (Courtesy Lia Jiangshan.)
3.	Add DEFINE_SRCU().  (Courtesy Lia Jiangshan.)
4.	Add DEFINE_STATIC_SRCU().  This cannot be emulated by
	"static DEFINE_SRCU()" due to forward-reference issues.
	(Courtesy Lia Jiangshan.)

							Thanx, Paul

 b/include/linux/srcu.h |   34 ++++++++++++++++++++++++++++++++++
 b/kernel/rcutorture.c  |   41 ++++++-----------------------------------
 b/kernel/srcu.c        |    8 ++++----
 3 files changed, 44 insertions(+), 39 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/