linux-kernel - Re: [PATCH] printk: Add loglevel for "do not print to consoles".

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4dae86af-1d9a-f5a8-cff6-aa91ec038a79@i-love.sakura.ne.jp>
Date:   Tue, 28 Apr 2020 20:33:21 +0900
From:   Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To:     Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc:     Petr Mladek <pmladek@...e.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        linux-kernel@...r.kernel.org, Dmitry Safonov <dima@...sta.com>,
        Michal Hocko <mhocko@...e.com>,
        Yafang Shao <laoar.shao@...il.com>
Subject: Re: [PATCH] printk: Add loglevel for "do not print to consoles".

On 2020/04/27 15:21, Sergey Senozhatsky wrote:
>> KERN_NO_CONSOLES is for type of messages where "saved for later analysis" is
>> important but "printed for immediate notification" is not important.
>> In other words, KERN_NO_CONSOLES is NOT for dying messages where "printed for
>> immediate notification" is important.
> 
> per-console loglevel is a user configurable parameter.
> KERN_NO_CONSOLES is a hard-coded policy.

But given that whether to use KERN_NO_CONSOLES is configurable via e.g. sysctl,
KERN_NO_CONSOLES will become a user configurable parameter. What's still wrong?