linux-kernel - Re: [patch] lock debugging: fix DEBUG_LOCKS_WARN_ON() & debug_locks

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: <20061219094017.GM21070@parisc-linux.org>
Date:	Tue, 19 Dec 2006 02:40:18 -0700
From:	Matthew Wilcox <matthew@....cx>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Jarek Poplawski <jarkao2@...pl>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...l.org>
Subject: Re: [patch] lock debugging: fix DEBUG_LOCKS_WARN_ON() & debug_locks_silent

On Tue, Dec 19, 2006 at 10:31:35AM +0100, Ingo Molnar wrote:
> 
> * Jarek Poplawski <jarkao2@...pl> wrote:
> 
> > >  	if (unlikely(c)) {						\
> > > -		if (debug_locks_silent || debug_locks_off())		\
> > > +		if (!debug_locks_silent && debug_locks_off())		\
> 
> btw., updated patch is below - the right order is to first do 
> debug_locks_off(), then debug_locks_silent.

Then how does one re-enable lock debugging after running the locking
testsuite?
-
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/