linux-kernel - Re: [PATCH] lockdep: disable lock debugging when kernel state becomes untrusted

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: <20060905095255.349e684c.lista1@comhem.se>
Date:	Tue, 5 Sep 2006 09:52:55 +0200
From:	Voluspa <lista1@...hem.se>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	akpm@...l.org, arjan@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lockdep: disable lock debugging when kernel state
 becomes untrusted

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/