From: Martijn de Gouw <martijn.de.gouw@prodrive.nl>
To: Anton Blanchard <anton@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
<linuxppc-dev@lists.ozlabs.org>
Cc: Micha Nelissen <micha.nelissen@prodrive.nl>
Subject: powerpc: Don't silently handle machine checks from userspace
Date: Fri, 2 Nov 2012 12:48:40 +0100 [thread overview]
Message-ID: <5093B318.9040305@prodrive.nl> (raw)
Hi,
The following commit:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=e49b1fae0ba4d06b29bd753a961abb447566bf4a
causes confusion, because it prints "Machine check in kernel mode" also when the bus error is actually in user space. When using RapidIO memory mapped access, and the device is removed or powered off, then a bus error is generated. This is on a freescale mpc8548 powerpc. Due to removing the user_mode check, the kernel calls "die" which causes the process to die with a BUS error, regardless of having a SIGBUS handler or not.
Therefore I request to put this check back, and even to put the removed code at the top of the machine check handler because there is no point in trying to recover from a user space bus error anyway.
Best regards,
--
Martijn de Gouw
Engineer
Prodrive B.V.
Mobile: +31 63 17 76 161
Phone: +31 40 26 76 200
next reply other threads:[~2012-11-02 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 11:48 Martijn de Gouw [this message]
2012-11-02 16:36 ` powerpc: Don't silently handle machine checks from userspace Scott Wood
2012-11-06 9:21 ` Micha Nelissen
2012-11-06 16:34 ` Scott Wood
2012-11-06 16:43 ` Micha Nelissen
2012-11-06 20:13 ` Scott Wood
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=5093B318.9040305@prodrive.nl \
--to=martijn.de.gouw@prodrive.nl \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=micha.nelissen@prodrive.nl \
/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.