From: Michael Ellerman <mpe@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Michael Ellerman <mpe@ellerman.id.au>
Cc: eajames@linux.ibm.com
Subject: Re: [PATCH] powerpc/47x: Fix 47x syscall return crash
Date: Sun, 15 Oct 2023 21:00:23 +1100 [thread overview]
Message-ID: <169736402375.957740.2565695828834016495.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20231010114750.847794-1-mpe@ellerman.id.au>
On Tue, 10 Oct 2023 22:47:50 +1100, Michael Ellerman wrote:
> Eddie reported that newer kernels were crashing during boot on his 476
> FSP2 system:
>
> kernel tried to execute user page (b7ee2000) - exploit attempt? (uid: 0)
> BUG: Unable to handle kernel instruction fetch
> Faulting instruction address: 0xb7ee2000
> Oops: Kernel access of bad area, sig: 11 [#1]
> BE PAGE_SIZE=4K FSP-2
> Modules linked in:
> CPU: 0 PID: 61 Comm: mount Not tainted 6.1.55-d23900f.ppcnf-fsp2 #1
> Hardware name: ibm,fsp2 476fpe 0x7ff520c0 FSP-2
> NIP: b7ee2000 LR: 8c008000 CTR: 00000000
> REGS: bffebd83 TRAP: 0400 Not tainted (6.1.55-d23900f.ppcnf-fs p2)
> MSR: 00000030 <IR,DR> CR: 00001000 XER: 20000000
> GPR00: c00110ac bffebe63 bffebe7e bffebe88 8c008000 00001000 00000d12 b7ee2000
> GPR08: 00000033 00000000 00000000 c139df10 48224824 1016c314 10160000 00000000
> GPR16: 10160000 10160000 00000008 00000000 10160000 00000000 10160000 1017f5b0
> GPR24: 1017fa50 1017f4f0 1017fa50 1017f740 1017f630 00000000 00000000 1017f4f0
> NIP [b7ee2000] 0xb7ee2000
> LR [8c008000] 0x8c008000
> Call Trace:
> Instruction dump:
> XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
> XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
> ---[ end trace 0000000000000000 ]---
>
> [...]
Applied to powerpc/fixes.
[1/1] powerpc/47x: Fix 47x syscall return crash
https://git.kernel.org/powerpc/c/f0eee815babed70a749d2496a7678be5b45b4c14
cheers
prev parent reply other threads:[~2023-10-15 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 11:47 [PATCH] powerpc/47x: Fix 47x syscall return crash Michael Ellerman
2023-10-10 12:59 ` Christophe Leroy
2023-10-15 10:00 ` Michael Ellerman [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=169736402375.957740.2565695828834016495.b4-ty@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=eajames@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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 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.