linux-kernel - Re: [PATCH] printk: Make 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]

Date:   Tue, 19 Jun 2018 09:31:02 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Hans de Goede <hdegoede@...hat.com>
Cc:     Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] printk: Make CONSOLE_LOGLEVEL_QUIET configurable

On Tue, 19 Jun 2018 13:57:26 +0200
Hans de Goede <hdegoede@...hat.com> wrote:

> The goal of passing the "quiet" option to the kernel is for the kernel
> to be quiet unless something really is wrong.
> 
> Sofar passing quiet has been (mostly) equivalent to passing
> loglevel=4 on the kernel commandline. Which means to show any messages
> with a level of KERN_ERR or higher severity on the console.
> 
> In practice this often does not result in a quiet boot though, since
> there are many false-positive or otherwise harmless error messages printed,
> defeating the purpose of the quiet option. Esp. the ACPICA code is really
> bad wrt this, but there are plenty of others too.
> 
> This commit makes CONSOLE_LOGLEVEL_QUIET configurable.
> 
> This for example will allow distros which want quiet to really mean quiet
> to set CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity
> then KERN_ERR (CRIT, ALERT, EMERG) get printed, avoiding an endless game
> of whack-a-mole silencing harmless error messages.
> 
> Signed-off-by: Hans de Goede <hdegoede@...hat.com>

Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.org>

-- Steve