All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mahesh Jagannath Salgaonkar <mahesh@linux.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>, linuxppc-dev@lists.ozlabs.org
Subject: Re: Injecting SLB miltihit crashes kernel 5.9.0-rc5
Date: Wed, 16 Sep 2020 12:42:54 +0530	[thread overview]
Message-ID: <59815d65-34e3-6604-67e3-c510aeb603c4@linux.ibm.com> (raw)
In-Reply-To: <20200915084302.GG29778@kitsune.suse.cz>

On 9/15/20 2:13 PM, Michal Suchánek wrote:
> Hello,
> 
> Using the SLB mutihit injection test module (which I did not write so I
> do not want to post it here) to verify updates on my 5.3 frankernekernel
> I found that the kernel crashes with Oops: kernel bad access.
> 
> I tested on latest upstream kernel build that I have at hand and the
> result is te same (minus the message - nothing was logged and the kernel
> simply rebooted).


Yes, SLB multihit recovery is broken upstream. Fix is on the way.


> 
> Since the whole effort to write a real mode MCE handler was supposed to
> prevent this maybe the SLB injection module should be added to the
> kernel selftests?

Yes. We are working on adding SLB injection selftest patches will be
posted soon.

Thanks,
-Mahesh.

> 
> Thanks
> 
> Michal
> 


      parent reply	other threads:[~2020-09-16  7:14 UTC|newest]

Thread overview: 10+ 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:06   ` Michal Suchanek
2020-09-15 18:16   ` peterz
2020-09-15 18:16     ` peterz
2020-09-16  9:00     ` Michal Suchánek
2020-09-16  9:00       ` Michal Suchánek
2020-09-16  7:12 ` Mahesh Jagannath Salgaonkar [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=59815d65-34e3-6604-67e3-c510aeb603c4@linux.ibm.com \
    --to=mahesh@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msuchanek@suse.de \
    /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.