linux-kernel - Re: 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-prev] [day] [month] [year] [list]

Message-ID: <20080728150100.GA32111@elte.hu>
Date:	Mon, 28 Jul 2008 17:01:00 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Valdis.Kletnieks@...edu
Cc:	mingo@...hat.com, peterz@...radead.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.26-<mumble> question regarding kernel/lockdep.c


* Valdis.Kletnieks@...edu <Valdis.Kletnieks@...edu> wrote:

> 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...

i guess most could/should be converted to pr_info() - and a couple of 
them need to be KERN_CONT.

	Ingo
--
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/