[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180130093640.r4a45m6eicmyeljc@pathway.suse.cz>
Date: Tue, 30 Jan 2018 10:36:40 +0100
From: Petr Mladek <pmladek@...e.com>
To: Dave Young <dyoung@...hat.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Andi Kleen <ak@...ux.intel.com>, sergey.senozhatsky@...il.com,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
kexec@...ts.infradead.org
Subject: Re: [PATCH V2] print kdump kernel loaded status in stack dump
On Tue 2018-01-30 17:07:29, Dave Young wrote:
> On 01/30/18 at 05:50pm, Sergey Senozhatsky wrote:
> > On (01/27/18 12:11), Dave Young wrote:
> > > It is useful to print kdump kernel loaded status in dump_stack()
> > > especially when panic happens so that we can differenciate
> > > kdump kernel early hang and a normal panic in a bug report.
> > >
> > > Signed-off-by: Dave Young <dyoung@...hat.com>
> >
> > Looks OK to me.
> >
> > Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Same here:
Reviewed-by: Petr Mladek <pmladek@...e.com>
> > I agree with Steven, would be better to move the whole thing
> > to lib/dump_stack.c
>
> If nobody has plan I can put it in my todo list, probably do it next
> week.
Sounds good.
JFYI, I would target these changes for 4.17. There was some discussion
about where and how to show the new information. IMHO, it would deserve
some gurgling in linux-next.
Best Regards,
Petr
Powered by blists - more mailing lists