[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181128091201.7dd80c92@gandalf.local.home>
Date: Wed, 28 Nov 2018 09:12:01 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Feng Tang <feng.tang@...el.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>,
Jonathan Corbet <corbet@....net>,
Thomas Gleixner <tglx@...utronix.de>,
John Stultz <john.stultz@...aro.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v3 0/2] panic: Add options to dump system info on panic
On Wed, 28 Nov 2018 17:54:00 +0800
Feng Tang <feng.tang@...el.com> wrote:
> Kernel panic issues are always painful to debug, partially
> because it's not easy to get enough information of the
> context when panic happens.
>
> And we have ramoops and kdump for that, while this commit
> tries to provide a easier way to show the system info by adding
> a cmdline parameter, referring some idea from sysrq handler.
>
> The patches have been used by us and did help on solving some nasty
> panic cases.
>
> Please help to review, thanks!
>
Looks fine to me.
Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
Although, I still wonder if we should add a comment stating that bit 4
is the same as ftrace_dump_on_oops.
-- Steve
Powered by blists - more mailing lists