[PATCH tip/core/urgent 0/10] v2: Fix RCU lockdep splats

From: Paul E. McKenney
Date: Fri Apr 30 2010 - 20:26:05 EST


Hello!

This patchset contains ten fixes for various lockdep splats. The first
two sets are repostings/revisions, the rest new. The new patches have
all been posted to LKML, but this is the first time for inclusion.

o rcu: v2: optionally leave lockdep enabled after RCU lockdep splat
This is a repost that makes the one-splat-per-boot the default,
but allows those who want multiple splats to get this behavior
via a new CONFIG_PROVE_RCU_REPEATEDLY configuration parameter.
(Original from Lai Jiangshan.)

o KEYS: Fix an RCU warning
KEYS: Fix an RCU warning in the reading of user keys
Fixes for RCU-lockdep splats from David Howells for
security/keys. Repost of http://lkml.org/lkml/2010/4/22/411.

o cgroup: Fix an RCU warning in cgroup_path()
cgroup: Fix an RCU warning in alloc_css_id()
sched: Fix an RCU warning in print_task()
cgroup: Check task_lock in task_subsys_state()
Fixes for new RCU-lockdep splats in cgroups and sched from
Li Zefan.

o memcg: css_id() must be called under rcu_read_lock()
Fixes for new RCU-lockdep splats in memcg from Kamazawa Hiroyuki.

o blk-cgroup: Fix RCU correctness warning in cfq_init_queue()
Fix for new RCU-lockdep splat in I/O scheduler from Vivek Goyal.

o vfs: fix RCU-lockdep false positive due to /proc access
Fix for new RCU-lockdep splat from fdtable.h, with much
debugging assist from Eric Dumazet.


b/block/cfq-iosched.c | 2 ++
b/include/linux/cgroup.h | 1 +
b/include/linux/fdtable.h | 3 ++-
b/include/linux/rcupdate.h | 15 +++++++++++----
b/kernel/cgroup.c | 12 +++++++++---
b/kernel/lockdep.c | 2 ++
b/kernel/sched_debug.c | 2 ++
b/lib/Kconfig.debug | 12 ++++++++++++
b/mm/memcontrol.c | 21 ++++++++++++++++-----
b/security/keys/request_key.c | 13 ++++++++-----
b/security/keys/user_defined.c | 3 ++-
kernel/cgroup.c | 4 ++--
12 files changed, 69 insertions(+), 21 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/