linux-kernel - Re: [PATCH v6 2/2] tty/sysrq: Replay kernel log messages on consoles via sysrq

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: Wed, 22 May 2024 17:31:12 +0200
From: Petr Mladek <pmladek@...e.com>
To: Sreenath Vijayan <sreenath.vijayan@...y.com>
Cc: john.ogness@...utronix.de, corbet@....net, gregkh@...uxfoundation.org,
	jirislaby@...nel.org, rdunlap@...radead.org, rostedt@...dmis.org,
	senozhatsky@...omium.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
	taichi.shimoyashiki@...y.com, daniel.palmer@...y.com,
	anandakumar.balasubramaniam@...y.com
Subject: Re: [PATCH v6 2/2] tty/sysrq: Replay kernel log messages on consoles
 via sysrq

On Wed 2024-03-13 15:52:52, Sreenath Vijayan wrote:
> When terminal is unresponsive, one cannot use dmesg to view
> the printk ring buffer messages. Also, syslog services may be
> disabled, especially on embedded systems, to check the messages
> after a reboot. In this scenario, replay the messages in printk
> ring buffer on consoles via sysrq by pressing sysrq+R.
> 
> The console loglevel will determine which all kernel log messages
> are displayed. The messages will be displayed only when
> console_trylock() succeeds. Users could repeat the sysrq key when
> it fails. If the owner of console subsystem lock is stuck,
> repeating the key won't work.
> 
> Suggested-by: Petr Mladek <pmladek@...e.com>
> Signed-off-by: Shimoyashiki Taichi <taichi.shimoyashiki@...y.com>
> Reviewed-by: John Ogness <john.ogness@...utronix.de>
> Signed-off-by: Sreenath Vijayan <sreenath.vijayan@...y.com>

Reviewed-by: Petr Mladek <pmladek@...e.com>

Best Regards,
Petr