[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190111162038.19771-1-pmladek@suse.com>
Date: Fri, 11 Jan 2019 17:20:35 +0100
From: Petr Mladek <pmladek@...e.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
linux-kernel@...r.kernel.org, Petr Mladek <pmladek@...e.com>
Subject: [PATCH 0/3] sysrq: Simple fixes and console visibility
The first two patches are simple bug fixes.
The last one is RFC to fix a bug report. It is not obvious
why sysrq debug operations show only the sysrq header on
the console. The filtering by console_loglevel makes
some sense. The level can actually be set by sysrq.
The solution implemented in the RFC is a warning. It is a simple
idea but the implementation is relatively complicated. Mainly
because all parts sysrq, printk, and consoles are
heavily configurable.
PS: I sent the first patch also separately. It was simple
and it was independent in my first draft of the RFC.
I am sorry for confusion.
Petr Mladek (3):
sysrq: Restore original console_loglevel when sysrq disabled
sysrq: Remove duplicated sysrq message
sysrq: Warn about insufficient console_loglevel
drivers/tty/sysrq.c | 34 ++++++++++++++++++++++++++++++----
include/linux/printk.h | 7 +++++++
kernel/printk/printk.c | 7 +++----
3 files changed, 40 insertions(+), 8 deletions(-)
--
2.13.7
Powered by blists - more mailing lists