linux-kernel - Re: [PATCH] printk: allow setting DEFAULT_MESSAGE

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]

Date:	Tue, 25 Jan 2011 17:01:37 -0800
From:	Mandeep Singh Baines <msb@...omium.org>
To:	Joe Perches <joe@...ches.com>
Cc:	Mandeep Singh Baines <msb@...omium.org>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	olofj@...omium.org
Subject: Re: [PATCH] printk: allow setting DEFAULT_MESSAGE_LEVEL via Kconfig

Joe Perches (joe@...ches.com) wrote:
> On Tue, 2011-01-25 at 15:57 -0800, Mandeep Singh Baines wrote:
> > To make it easier to audit dmesg, we'd like to make
> > DEFAULT_MESSAGE_LEVEL Kconfig-settable. That way we can set it to
> > KERN_NOTICE and audit any messages <= KERN_WARNING.
> 
> Seems sensible, but mightn't it be better to make sure
> that all printks use a specific KERN_<level> rather
> than check that printks without a KERN_<level> are
> emitted at a selectable level?
> 

Can we do both? I was planning sending cleanup patches as well but expected
that process to take a while. The simplest thing would to set all these
to KERN_WARNING but that's not correct and leaves me back where I started.
The correct thing would be to set each printk to an appropriate level.
Determining appropriate level will take some discussion (so a long term
project).

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