From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Dave Young <dyoung@redhat.com>
Cc: Petr Mladek <pmladek@suse.com>, Andi Kleen <ak@linux.intel.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
sergey.senozhatsky@gmail.com, akpm@linux-foundation.org
Subject: Re: [PATCH V2] print kdump kernel loaded status in stack dump
Date: Tue, 30 Jan 2018 17:50:55 +0900 [thread overview]
Message-ID: <20180130085055.GA569@jagdpanzerIV> (raw)
In-Reply-To: <20180127041129.GA29016@dhcp-128-65.nay.redhat.com>
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@redhat.com>
Looks OK to me.
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
I agree with Steven, would be better to move the whole thing
to lib/dump_stack.c
-ss
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Dave Young <dyoung@redhat.com>
Cc: Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andi Kleen <ak@linux.intel.com>,
sergey.senozhatsky@gmail.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, kexec@lists.infradead.org
Subject: Re: [PATCH V2] print kdump kernel loaded status in stack dump
Date: Tue, 30 Jan 2018 17:50:55 +0900 [thread overview]
Message-ID: <20180130085055.GA569@jagdpanzerIV> (raw)
In-Reply-To: <20180127041129.GA29016@dhcp-128-65.nay.redhat.com>
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@redhat.com>
Looks OK to me.
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
I agree with Steven, would be better to move the whole thing
to lib/dump_stack.c
-ss
next prev parent reply other threads:[~2018-01-30 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 4:11 [PATCH V2] print kdump kernel loaded status in stack dump Dave Young
2018-01-27 4:11 ` Dave Young
2018-01-30 8:50 ` Sergey Senozhatsky [this message]
2018-01-30 8:50 ` Sergey Senozhatsky
2018-01-30 9:07 ` Dave Young
2018-01-30 9:07 ` Dave Young
2018-01-30 9:36 ` Petr Mladek
2018-01-30 9:36 ` Petr Mladek
2018-01-31 12:39 ` Simon Horman
2018-01-31 12:39 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180130085055.GA569@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.