From: Nicholas Piggin <npiggin@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc: fix graceful debugger recovery
Date: Thu, 10 Nov 2016 15:24:59 +1100 [thread overview]
Message-ID: <20161110152459.7ab453f5@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <87mvh8jev4.fsf@concordia.ellerman.id.au>
On Thu, 10 Nov 2016 12:35:59 +1100
Michael Ellerman <mpe@ellerman.id.au> wrote:
> Nicholas Piggin <npiggin@gmail.com> writes:
>
> > When exiting xmon with 'x' (exit and recover), oops_begin bails
> > out immediately, but die then calls __die() and oops_end(), which
> > cause a lot of bad things to happen.
>
> In fact oops_begin() returns 1, which oops_end() then passes directly to
> raw_local_irq_restore() as flags. On 64-bit that actually works because
> arch_local_irq_restore() takes just "en" (enable), not real flags. But
> on 32-bit it's supposed to be the MSR value. So that's impressively
> broken.
Yeah, I guess most of the time you either go to debugger with
sysrq, or in case of a crash don't try to graceful recover.
When sending debug NMIs down via system reset it becomes a problem!
>
> > If the debugger was attached then went to graceful recovery, exit
> > from die() immediately.
>
> Right. Crucially it doesn't change anything in terms of the actual logic
> of oops_begin(), ie. previously oops_begin() did nothing prior to
> calling debugger(), and after this patch that remains the same (which
> you did mention above but just spelling it out for myself).
Right.
Thanks,
Nick
next prev parent reply other threads:[~2016-11-10 4:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 12:14 [PATCH 0/2] powerpc: oops fixes Nicholas Piggin
2016-11-08 12:14 ` [PATCH 1/2] powerpc: fix graceful debugger recovery Nicholas Piggin
2016-11-10 1:35 ` Michael Ellerman
2016-11-10 4:24 ` Nicholas Piggin [this message]
2016-11-10 10:25 ` Michael Ellerman
2016-11-22 0:34 ` [1/2] " Michael Ellerman
2016-11-08 12:14 ` [PATCH 2/2] powerpc: fix second nested oops hang Nicholas Piggin
2016-11-22 0:34 ` [2/2] " Michael Ellerman
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=20161110152459.7ab453f5@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).