linux-kernel - 2.6.26-<mumble> question regarding kernel/lockdep.c

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

Message-ID: <42591.1216772410@turing-police.cc.vt.edu>
Date:	Tue, 22 Jul 2008 20:20:10 -0400
From:	Valdis.Kletnieks@...edu
To:	mingo@...hat.com, peterz@...radead.org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: 2.6.26-<mumble> question regarding kernel/lockdep.c

I was chasing after some weird behavior with lockdep, and I found that
almost none of the printk() calls in kernel/lockdep.c have a KERN_FOO
level specified.

It looks like it could use patching, but before I code something, I
need to know if the patch should be doing:

a) Adding the missing KERN_FOO levels..
or
b) Adding a comment explaining the subtle reason they're not there...

Content of type "application/pgp-signature" skipped