linux-kernel - [GIT PULL] RCU fixes for 2.6.34

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]

Message-ID: <20100504033616.GA6155@linux.vnet.ibm.com>
Date:	Mon, 3 May 2010 20:36:16 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	mingo@...e.hu
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	a.p.zijlstra@...llo.nl, tglx@...utronix.de
Subject: [GIT PULL] RCU fixes for 2.6.34

Hello, Ingo,

Here are RCU fixes for 2.6.34, mainly RCU-lockdep fixes:

git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git urgent-to-mingo

This set excludes the three needing Acked-by, and also excludes the
commits targeted for 2.6.35.

							Thanx, Paul

------------------>
David Howells (2)
    KEYS: Fix an RCU warning in the reading of user keys
    KEYS: Fix an RCU warning

Lai Jiangshan (1)
    rcu: v2: optionally leave lockdep enabled after RCU lockdep splat

Li Zefan (4)
    cgroup: Check task_lock in task_subsys_state()
    sched: Fix an RCU warning in print_task()
    cgroup: Fix an RCU warning in alloc_css_id()
    cgroup: Fix an RCU warning in cgroup_path()

 include/linux/cgroup.h       |    1 +
 include/linux/rcupdate.h     |   15 +++++++++++----
 kernel/cgroup.c              |   16 +++++++++++-----
 kernel/lockdep.c             |    2 ++
 kernel/sched_debug.c         |    2 ++
 lib/Kconfig.debug            |   12 ++++++++++++
 security/keys/request_key.c  |   13 ++++++++-----
 security/keys/user_defined.c |    3 ++-
 8 files changed, 49 insertions(+), 15 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/