linux-kernel - [PATCH RFC tip/core/rcu 0/2] rcu: make RCU lockdep handle early boot in organized manner

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:	Mon, 1 Mar 2010 11:03:29 -0800
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@...ymtl.ca,
	josh@...htriplett.org, dvhltc@...ibm.com, niv@...ibm.com,
	tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org,
	Valdis.Kletnieks@...edu, dhowells@...hat.com
Subject: [PATCH RFC tip/core/rcu 0/2] rcu: make RCU lockdep handle early
	boot in organized manner

Hello!

This patch set makes RCU lockdep handle early boot in an organized
manner:

1.	Make rcu_read_lock_held(), rcu_read_lock_bh_held(),
	rcu_read_lock_sched_held(), and rcu_dereference_check()
	suppress complaints if !rcu_scheduler_active.  The rationale
	for this approach is that RCU grace periods are handled very
	differently during early boot, and rcu_scheduler_active marks
	the point that normal runtime RCU behavior starts.

2.	Remove the !rcu_scheduler_active check from calls to
	rcu_dereference_check(), because rcu_dereference_check() already
	does the check in question.

Testing in progress, but want to get these out for review.

							Thanx, Paul

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

 cgroup.h   |    2 --
 rcupdate.h |   27 +++++++++++++++++----------
 2 files changed, 17 insertions(+), 12 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/