linux-kernel - Re: [RFC][PATCH 0/6] using lockdep to validate rcu usage

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: <20070919133814.GA3731@elte.hu>
Date:	Wed, 19 Sep 2007 15:38:14 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Nick Piggin <nickpiggin@...oo.com.au>
Subject: Re: [RFC][PATCH 0/6] using lockdep to validate rcu usage


* Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:

> This patch set uses lockdep to validate rcu usage.
> 
> It annotates rcu_read_{,un}lock{,_bh}() to catch imbalances. And 
> further uses that information to establish a proper context for 
> rcu_dereference().
> 
> It also separates implicit from explicit preempt_disable() usage, in 
> order to separate rcu_dereference() from the locking model.
> 
> A kernel (2.6.23-rc4-mm1) with these patches boots but does have some 
> funnies - I suspect it calls printf from places it doesn't like.
> 
> The first patch should be safe to apply, the rest is RFC.

great work! The patches look good to me.

Signed-off-by: Ingo Molnar <mingo@...e.hu>

	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/