[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190918124801.04fe999d@gandalf.local.home>
Date: Wed, 18 Sep 2019 12:48:01 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Petr Mladek <pmladek@...e.com>
Cc: John Ogness <john.ogness@...utronix.de>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Andrea Parri <parri.andrea@...il.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
Paul Turner <pjt@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Theodore Ts'o <tytso@....edu>,
Prarit Bhargava <prarit@...hat.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: printk meeting at LPC
On Wed, 18 Sep 2019 18:41:55 +0200
Petr Mladek <pmladek@...e.com> wrote:
> Regarding SysRq. I could imagine introducing another SysRq that
> would just call panic(). I mean that it would try to flush the
> logs and reboot in the most safe way.
You mean sysrq-c ?
-- Steve
Powered by blists - more mailing lists