All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
	josh@joshtriplett.org, dvhltc@us.ibm.com, niv@us.ibm.com,
	tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
	Valdis.Kletnieks@vt.edu, dhowells@redhat.com
Subject: [PATCH tip/core/rcu 0/4] rcu: suppress RCU lockdep early-boot warnings and fixes
Date: Wed, 3 Mar 2010 07:46:38 -0800	[thread overview]
Message-ID: <20100303154638.GA8576@linux.vnet.ibm.com> (raw)

Hello!

This patch series suppresses early-boot RCU-lockdep warnings and fixes
a couple of other RCU lockdep issues:

1.	Use a wrapper function to query lockdep about tasklist_lock
	instead of (re-)exporting tasklist_lock to modules.

2.	Suppress early-boot RCU-lockdep warnings.

3.	Revert an earlier lockdep-RCU patch that manually checked for
	early boot.

4.	Add a couple of variables to the lockdep_rcu_dereference()
	output.

Testing identified a couple of lockdep splats that I thought were due
to early boot issues, but which turned out to be not -quite- that early.
These will be dealt with by a pair of later patches.

							Thanx, Paul

 include/linux/cgroup.h   |    2 --
 include/linux/cred.h     |    2 +-
 include/linux/rcupdate.h |   35 ++++++++++++++++++++++++++---------
 include/linux/sched.h    |    4 ++++
 kernel/exit.c            |    2 +-
 kernel/fork.c            |    9 ++++++++-
 kernel/lockdep.c         |    2 +-
 kernel/pid.c             |    5 +++--
 lib/locking-selftest.c   |    6 +++++-
 9 files changed, 49 insertions(+), 18 deletions(-)

             reply	other threads:[~2010-03-03 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 15:46 Paul E. McKenney [this message]
2010-03-03 15:46 ` [PATCH tip/core/rcu 1/4] rcu: use wrapper function instead of exporting tasklist_lock Paul E. McKenney
2010-03-04 16:31   ` [tip:core/urgent] rcu: Use " tip-bot for Paul E. McKenney
2010-03-03 15:46 ` [PATCH tip/core/rcu 2/4] rcu: suppress RCU lockdep warnings during early boot Paul E. McKenney
2010-03-04 11:12   ` Ingo Molnar
2010-03-04 11:44     ` Ingo Molnar
2010-03-04 20:35       ` Paul E. McKenney
2010-03-04 20:36     ` Paul E. McKenney
2010-03-04 16:33   ` [tip:core/urgent] rcu: Suppress " tip-bot for Paul E. McKenney
2010-03-03 15:46 ` [PATCH tip/core/rcu 3/4] rcu: revert 1883c79a: early boot now handled by lockdep-RCU Paul E. McKenney
2010-03-04 16:32   ` [tip:core/urgent] rcu, cgroup: Relax the check in task_subsys_state() as early boot is " tip-bot for Paul E. McKenney
2010-03-03 15:46 ` [PATCH tip/core/rcu 4/4] rcu: add control variables to lockdep_rcu_dereference() diagnostics Paul E. McKenney
2010-03-04 16:32   ` [tip:core/urgent] rcu: Add " tip-bot for Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100303154638.GA8576@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.