From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm64: Add dump_backtrace() in show_regs
Date: Thu, 25 May 2017 11:58:32 +0100 [thread overview]
Message-ID: <20170525105832.GA2859@arm.com> (raw)
In-Reply-To: <20170524100949.GA24574@leverpostej>
On Wed, May 24, 2017 at 11:09:49AM +0100, Mark Rutland wrote:
> On Tue, May 09, 2017 at 09:53:37AM +0800, Kefeng Wang wrote:
> > Generic code expects show_regs() to dump the stack, but arm64's
> > show_regs() does not. This makes it hard to debug softlockups and
> > other issues that result in show_regs() being called.
> >
> > This patch updates arm64's show_regs() to dump the stack, as common
> > code expects.
> >
> > Acked-by: Mark Rutland <mark.rutland@arm.com>
> > Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
[...]
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index 0805b44..f452fcc 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -728,8 +728,6 @@ static int bug_handler(struct pt_regs *regs, unsigned int esr)
> break;
>
> case BUG_TRAP_TYPE_WARN:
> - /* Ideally, report_bug() should backtrace for us... but no. */
> - dump_backtrace(regs, NULL);
> break;
>
> default:
>
> ... since report_bug() will call show_regs(), and dump the stack itself
> now.
>
> With that change, these patches will also fix *_ONCE() traps spewing
> backtraces every time they're invoked, which was a side-effect of
> commit:
>
> 19d436268dde9538 ("debug: Add _ONCE() logic to report_bug()")
>
> Would you mind folding that into a v3?
I've queued this locally, so I can just fold that in too. No need to repost.
I'll push what I have at -rc3.
Cheers,
Will
prev parent reply other threads:[~2017-05-25 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 13:56 [PATCH 1/2] arm64: Call __show_regs directly Kefeng Wang
2017-05-08 13:56 ` [PATCH 2/2] arm64: Add dump_backtrace() in show_regs Kefeng Wang
2017-05-08 15:04 ` Mark Rutland
2017-05-09 1:23 ` Kefeng Wang
2017-05-08 14:55 ` [PATCH 1/2] arm64: Call __show_regs directly Mark Rutland
2017-05-09 1:53 ` [PATCH v2 " Kefeng Wang
2017-05-09 1:53 ` [PATCH v2 2/2] arm64: Add dump_backtrace() in show_regs Kefeng Wang
2017-05-24 10:09 ` Mark Rutland
2017-05-25 10:58 ` Will Deacon [this message]
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=20170525105832.GA2859@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).