Date: Tue, 5 Sep 2006 09:52:55 +0200
From: Voluspa <lista1@comhem.se>
To: Ingo Molnar <mingo@elte.hu>
Cc: akpm@osdl.org, arjan@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lockdep: disable lock debugging when kernel state
 becomes untrusted
Message-Id: <20060905095255.349e684c.lista1@comhem.se>
In-Reply-To: <20060905071501.GA2765@elte.hu>
References: <20060814030954.c3a57e05.lista1@comhem.se>
	<20060813184159.b536736f.akpm@osdl.org>
	<20060905071501.GA2765@elte.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 696
Lines: 22

On Tue, 5 Sep 2006 09:15:01 +0200 Ingo Molnar wrote:
> 
> * Andrew Morton wrote:
> 
> > That would appear to be a bug.  debug_locks_off() is running 
> > console_verbose() waaaay after the locking selftest code has 
> > completed.
> 
> debug_locks_off() should only be used when a real bug is being
> displayed 
> - which isnt the case when we call add_taint(). The patch below
> should fix this.

Thanks, it works as advertised.

Mvh
Mats Johannesson
-
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/