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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Fri, 24 Apr 2020 12:21:46 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc:     Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        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 Sat, 25 Apr 2020 01:10:15 +0900
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp> wrote:

> KERN_NO_CONSOLES is a mechanism for implementing user decided policy. As long as
> userspace can control whether to use KERN_NO_CONSOLES (e.g. sysctl), there should
> be no problem with adding KERN_NO_CONSOLES (i.e. this patch) to the kernel side.

How would you define what gets "KERN_NO_CONSOLES"? Is it going to be a
sysctl switch?

Also, how does one control the log level of prints with KERN_NO_CONSOLES?

-- Steve