[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181211082616.GC521@jagdpanzerIV>
Date: Tue, 11 Dec 2018 17:26:16 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Feng Tang <feng.tang@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
akpm@...ux-foundation.org, bp@...e.de, keescook@...omium.org,
mm-commits@...r.kernel.org, sergey.senozhatsky@...il.com,
stable@...r.kernel.org, tglx@...utronix.de,
Steven Rostedt <rostedt@...dmis.org>,
Sasha Levin <sashal@...nel.org>,
Andi Kleen <ak@...ux.intel.com>, linux-kernel@...r.kernel.org
Subject: Re: + panic-avoid-the-extra-noise-dmesg.patch added to -mm tree
On (12/11/18 09:22), Petr Mladek wrote:
> I suggested to clear the panic_blinking (or whatever name) in
> __handle_sysrq(). The idea is that sysrq needs manual intervention.
> It allows to see the original message before it gets overridden
> by a potential sysrq-related output.
Ah, indeed. Sounds good.
> It assumes that sysrq is the only interesting operation when
> printk() might be useful at this state.
Agreed. Makes sense.
-ss
Powered by blists - more mailing lists