linux-kernel - Re: [GIT PULL] Additional 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100506062250.GC1172@elte.hu>
Date:	Thu, 6 May 2010 08:22:50 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Jens Axboe <jens.axboe@...cle.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	a.p.zijlstra@...llo.nl, tglx@...utronix.de
Subject: Re: [GIT PULL] Additional RCU fixes for 2.6.34


* Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:

> Hello, Ingo,
> 
> Here are three more RCU-lockdep fixes for 2.6.34:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/urgent
> 
> 							Thanx, Paul
> 
> ------------------>
> Vivek Goyal <vgoyal@...hat.com> (1)
> 	blk-cgroup: Fix RCU correctness warning in cfq_init_queue()
> 
> Paul E. McKenney <paulmck@...ux.vnet.ibm.com> (2)
> 	vfs: fix RCU-lockdep false positive due to /proc access
> 	memcg: css_id() must be called under rcu_read_lock()
> 
>  block/cfq-iosched.c      |    2 ++
>  include/linux/fdtable.h  |    3 ++-
>  include/linux/rcupdate.h |   11 +++++++++++
>  kernel/rcupdate.c        |   11 +++++++++++
>  mm/memcontrol.c          |   21 ++++++++++++++++-----
>  5 files changed, 42 insertions(+), 6 deletions(-)

Pulled, thanks Paul!

Jens, is that blk-cgroup fix from Vivek fine to you via this route?

Thanks,

	Ingo
--
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/