Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756871Ab1DHNci (ORCPT ); Fri, 8 Apr 2011 09:32:38 -0400 Received: from casper.infradead.org ([85.118.1.10]:34388 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752452Ab1DHNch convert rfc822-to-8bit (ORCPT ); Fri, 8 Apr 2011 09:32:37 -0400 Subject: Re: Q. lockdep_assert_held() and lockdep_off/on() From: Peter Zijlstra To: "J. R. Okajima" Cc: Ingo Molnar , linux-kernel@vger.kernel.org In-Reply-To: <9752.1302268789@jrobl> References: <9752.1302268789@jrobl> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Fri, 08 Apr 2011 15:32:30 +0200 Message-ID: <1302269550.9086.142.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 758 Lines: 23 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/