From: peterz@infradead.org
To: Michal Suchanek <msuchanek@suse.de>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Santosh Sivaraj <santosh@fossix.org>,
Alistair Popple <alistair@popple.id.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>,
linux-kernel@vger.kernel.org, Jordan Niethe <jniethe5@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Ganesh Goudar <ganeshgr@linux.ibm.com>,
stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH] Revert "powerpc/64s: machine check interrupt update NMI accounting"
Date: Tue, 15 Sep 2020 20:16:42 +0200 [thread overview]
Message-ID: <20200915181642.GF2674@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200915180659.12503-1-msuchanek@suse.de>
On Tue, Sep 15, 2020 at 08:06:59PM +0200, Michal Suchanek wrote:
> This reverts commit 116ac378bb3ff844df333e7609e7604651a0db9d.
>
> This commit causes the kernel to oops and reboot when injecting a SLB
> multihit which causes a MCE.
>
> Before this commit a SLB multihit was corrected by the kernel and the
> system continued to operate normally.
>
> cc: stable@vger.kernel.org
> Fixes: 116ac378bb3f ("powerpc/64s: machine check interrupt update NMI accounting")
> Signed-off-by: Michal Suchanek <msuchanek@suse.de>
Ever since 69ea03b56ed2 ("hardirq/nmi: Allow nested nmi_enter()")
nmi_enter() supports nesting natively.
next prev parent reply other threads:[~2020-09-15 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 8:43 Injecting SLB miltihit crashes kernel 5.9.0-rc5 Michal Suchánek
2020-09-15 12:54 ` Michael Ellerman
2020-09-16 0:51 ` Nicholas Piggin
2020-09-15 18:06 ` [PATCH] Revert "powerpc/64s: machine check interrupt update NMI accounting" Michal Suchanek
2020-09-15 18:16 ` peterz [this message]
2020-09-16 9:00 ` Michal Suchánek
2020-09-16 7:12 ` Injecting SLB miltihit crashes kernel 5.9.0-rc5 Mahesh Jagannath Salgaonkar
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=20200915181642.GF2674@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alistair@popple.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=ganeshgr@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jniethe5@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=msuchanek@suse.de \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=rppt@kernel.org \
--cc=santosh@fossix.org \
--cc=stable@vger.kernel.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).