linux-kernel - Re: [PATCH] printk: add Kconfig for default console loglevel

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]

Message-ID: <1311699705.15386.20.camel@Joe-Laptop>
Date:	Tue, 26 Jul 2011 10:01:45 -0700
From:	Joe Perches <joe@...ches.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Dave Reisner <d@...conindy.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Dave Reisner <dreisner@...hlinux.org>
Subject: Re: [PATCH] printk: add Kconfig for default console loglevel

On Tue, 2011-07-26 at 09:37 -0700, Randy Dunlap wrote:
> On Tue, 26 Jul 2011 11:33:51 -0400 Dave Reisner wrote:
> > Keep the historical default of 7, but allow distributions and users to
> > tune this value instead of requiring a kernel cmdline parameter.
> Please explain how this is different from what is already in lib/Kconfig.debug:
> config DEFAULT_MESSAGE_LOGLEVEL
> 	int "Default message log level (1-7)"
> 	range 1 7
> 	default "4"
> 	help
> 	  Default log level for printk statements with no specified priority.

DEFAULT_MESSAGE_LOGLEVEL sets a KERN_<level> for
printks without a KERN_<level>.

> > +config DEFAULT_CONSOLE_LOGLEVEL
> > +	int "Default console log level (1-7)"
> > +	range 1 7
> > +	default "7"
> > +	help
> > +	  Default console log level setting for printk statements.
> > +
> > +	  This was hard-coded to KERN_INFO (7) since at least 2.6.12. You may
> > +	  wish to turn this down to 4 for a quieter console.
> > +

This allows 'unimportant' messages to not be shown by default.

I think there are lots of KERN_INFO messages that are
miscategorized.  This change might cause some shifting
of KERN_<level>s in the future, so it's OK by me. 

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