Re: [PATCH] sysrq: Restore original console_loglevel when sysrq disabled

2019-01-14 Thread Petr Mladek
On Mon 2019-01-14 14:36:42, Sergey Senozhatsky wrote: > On (01/11/19 16:32), Petr Mladek wrote: > > The same problem is with the sysrq header line. It uses the trick > > with console_loglevel by intention. We want to show it but > > it is not really an error message > > May be. > > I usually see

Re: [PATCH] sysrq: Restore original console_loglevel when sysrq disabled

2019-01-13 Thread Sergey Senozhatsky
On (01/11/19 16:32), Petr Mladek wrote: > The same problem is with the sysrq header line. It uses the trick > with console_loglevel by intention. We want to show it but > it is not really an error message May be. I usually see it as an "error". My case: systemd sets sysrq on every boot to /

Re: [PATCH] sysrq: Restore original console_loglevel when sysrq disabled

2019-01-11 Thread Steven Rostedt
On Fri, 11 Jan 2019 22:07:29 +0900 Sergey Senozhatsky wrote: > On (01/11/19 13:45), Petr Mladek wrote: > > The sysrq header line is printed with an increased loglevel > > to provide users some positive feedback. > > > > The original loglevel is not restored when the sysrq operation > > is disabl

Re: [PATCH] sysrq: Restore original console_loglevel when sysrq disabled

2019-01-11 Thread Petr Mladek
On Fri 2019-01-11 22:07:29, Sergey Senozhatsky wrote: > On (01/11/19 13:45), Petr Mladek wrote: > > The sysrq header line is printed with an increased loglevel > > to provide users some positive feedback. > > > > The original loglevel is not restored when the sysrq operation > > is disabled. This

Re: [PATCH] sysrq: Restore original console_loglevel when sysrq disabled

2019-01-11 Thread Sergey Senozhatsky
On (01/11/19 13:45), Petr Mladek wrote: > The sysrq header line is printed with an increased loglevel > to provide users some positive feedback. > > The original loglevel is not restored when the sysrq operation > is disabled. This bug was introduced in 2.6.12 (pre-git-history) > by the commit ("A