linux-kernel - Re: Q. lockdep_assert_held() and lockdep

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] [day] [month] [year] [list]

Message-ID: <1302269550.9086.142.camel@twins>
Date:	Fri, 08 Apr 2011 15:32:30 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	"J. R. Okajima" <hooanon05@...oo.co.jp>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: Q. lockdep_assert_held() and lockdep_off/on()

On Fri, 2011-04-08 at 22:19 +0900, J. R. Okajima wrote:
> Hello Peter Zijlstra and Ingo Molnar,
> 
> May I ask you a question about the commit
> 	f607c66 2009-08-02 lockdep: Introduce lockdep_assert_held()
> 
> In short, should lockdep_assert_held() support ->lockdep_recursion?

Probably, however

> Its current definition is
> #define lockdep_assert_held(l) WARN_ON(debug_locks && !lockdep_is_held(l))
> 
> When someone somewhere calls lockdep_off() and executes some memory

you're not supposed to do that..


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