public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Shreyas Joshi <shreyas.joshi@biamp.com>,
	shreyasjoshi15@gmail.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: [RFC 0/2] printk: Official way to mute consoles
Date: Thu, 22 Oct 2020 13:42:26 +0200	[thread overview]
Message-ID: <20201022114228.9098-1-pmladek@suse.com> (raw)

The long discussion about handling empty console= came up with several
problems. This patchset tries to solve the two original problems
with empty console="" parameter:

  + Prevent the potential crash by registering console for /dev/console.
  + Prevent the performance regression by muting the consoles.

IMHO, the patchset makes sense on its own. It fixes a regression. It seems
that people want this functionality [1][2][3].

Note that there are still some problems that might be solved later:

  + Invalid console=bla name might still prevent registering any console.

  + The kernel should not crash even when /dev/console does not point
    to any real console. 

  + Should we add some fallback for stdin, stdout, and stderr when /dev/console
    can't be opened? For example, /dev/null?
    
  + How user space handle missing none-console associated with /dev/console?

[1] https://www.programmersought.com/article/19374022450/
[2] https://developer.toradex.com/knowledge-base/how-to-disable-enable-debug-messages-in-linux
[3] https://unix.stackexchange.com/questions/117926/try-to-disable-console-output-console-null-doesnt-work


Petr Mladek (2):
  printk: Add kernel parameter: mute_console
  printk: Restore and document obsolete ways to disable console output

 .../admin-guide/kernel-parameters.txt         | 11 +++++++
 kernel/printk/printk.c                        | 30 +++++++++++++++++--
 2 files changed, 39 insertions(+), 2 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-10-22 11:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 11:42 Petr Mladek [this message]
2020-10-22 11:42 ` [RFC 1/2] printk: Add kernel parameter: mute_console Petr Mladek
2020-10-22 13:10   ` John Ogness
2020-10-22 14:15     ` Guenter Roeck
2020-10-22 14:53       ` John Ogness
2020-10-23 11:49         ` Petr Mladek
2020-10-23 14:52           ` Guenter Roeck
2020-10-22 13:45   ` Steven Rostedt
2020-10-22 14:22     ` Guenter Roeck
2020-10-23  9:46     ` Petr Mladek
2020-10-23  0:33   ` Sergey Senozhatsky
2020-10-23 12:11     ` Petr Mladek
2020-10-23 15:59   ` Linus Torvalds
2020-10-22 11:42 ` RFC 2/2] printk: Restore and document obsolete ways to disable console output Petr Mladek
2020-10-22 14:23   ` Guenter Roeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201022114228.9098-1-pmladek@suse.com \
    --to=pmladek@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=shreyas.joshi@biamp.com \
    --cc=shreyasjoshi15@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox