linux-kernel.vger.kernel.org archive mirror
 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,
	eric.dumazet@gmail.com
Subject: [PATCH tip/core/urgent 0/2] RCU lockdep fix and shrink RCU API
Date: Thu, 18 Mar 2010 12:25:13 -0700	[thread overview]
Message-ID: <20100318192513.GA10832@linux.vnet.ibm.com> (raw)

Hello!

This set has two patches, one from Lai Jiangshan that fixes RCU lockdep's
rcu_read_lock_sched_held() to correctly interpret things like
local_irq_disable() as starting a valid RCU-sched read-side critical
section, and one from Alexey Dobriyan that removes several useless
members of the RCU API.

							Thanx, Paul

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

 b/Documentation/DocBook/kernel-locking.tmpl   |    8 --------
 b/arch/powerpc/mm/pgtable.c                   |    1 -
 b/block/cfq-iosched.c                         |    1 -
 b/block/genhd.c                               |    1 -
 b/drivers/staging/batman-adv/hard-interface.c |    1 -
 b/fs/file.c                                   |    3 ---
 b/fs/fs-writeback.c                           |    1 -
 b/fs/partitions/check.c                       |    1 -
 b/include/linux/init_task.h                   |    1 -
 b/include/linux/rcupdate.h                    |    4 ++--
 b/mm/backing-dev.c                            |    1 -
 b/mm/slob.c                                   |    1 -
 b/security/selinux/avc.c                      |    1 -
 b/security/selinux/netnode.c                  |    2 --
 include/linux/rcupdate.h                      |    6 ------
 15 files changed, 2 insertions(+), 31 deletions(-)

             reply	other threads:[~2010-03-18 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 19:25 Paul E. McKenney [this message]
2010-03-18 19:25 ` [PATCH tip/core/urgent 1/2] rcu: local_irq_disable() also delimits RCU_SCHED read-site critical sections Paul E. McKenney
2010-03-18 22:03   ` [tip:core/urgent] rcu: Fix local_irq_disable() CONFIG_PROVE_RCU=y false positives tip-bot for Lai Jiangshan
2010-03-18 19:25 ` [PATCH tip/core/urgent 2/2] rcu: remove INIT_RCU_HEAD, RCU_HEAD_INIT, RCU_HEAD Paul E. McKenney
2010-03-18 19:35   ` Mathieu Desnoyers
2010-03-18 20:03     ` Paul E. McKenney
2010-03-18 20:22       ` Mathieu Desnoyers
2010-03-18 21:04         ` Paul E. McKenney
2010-03-19  0:34           ` Mathieu Desnoyers

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=20100318192513.GA10832@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=eric.dumazet@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).