[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1491887293-3815-1-git-send-email-ravi.bangoria@linux.vnet.ibm.com>
Date: Tue, 11 Apr 2017 10:38:13 +0530
From: Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
To: mpe@...erman.id.au
Cc: benh@...nel.crashing.org, paulus@...ba.org, npiggin@...il.com,
aneesh.kumar@...ux.vnet.ibm.com, bsingharora@...il.com,
chris@...troguy.com, viro@...iv.linux.org.uk,
christophe.leroy@....fr, linuxppc-dev@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, anton@...ba.org,
naveen.n.rao@...ux.vnet.ibm.com,
Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
Subject: [PATCH v2] ppc64/kprobe: Fix oops when kprobed on 'stdu' instruction
If we set a kprobe on a 'stdu' instruction on powerpc64, we see a kernel
OOPS:
[ 1275.165932] Bad kernel stack pointer cd93c840 at c000000000009868
[ 1275.166378] Oops: Bad kernel stack pointer, sig: 6 [#1]
...
GPR00: c000001fcd93cb30 00000000cd93c840 c0000000015c5e00 00000000cd93c840
...
[ 1275.178305] NIP [c000000000009868] resume_kernel+0x2c/0x58
[ 1275.178594] LR [c000000000006208] program_check_common+0x108/0x180
Basically, on 64 bit system, when user probes on 'stdu' instruction,
kernel does not emulate actual store in emulate_step itself because it
may corrupt exception frame. So kernel does actual store operation in
exception return code i.e. resume_kernel().
resume_kernel() loads the saved stack pointer from memory using lwz,
effectively loading a corrupt (32bit) address, causing the kernel crash.
Fix this by loading the 64bit value instead.
Fixes: be96f63375a1 ("powerpc: Split out instruction analysis part of emulate_step()")
Signed-off-by: Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
Reviewed-by: Naveen N. Rao <naveen.n.rao@...ux.vnet.ibm.com>
---
History:
Commit 8e9f69371536 ("powerpc/kprobe: Don't emulate store when kprobe
stwu r1") fixed exception frame corruption for 32 bit system which uses
'stwu' instruction for stack frame allocation. This commit also added
code for 64 bit system but did not enabled it for 'stdu' instruction.
So 'stdu' instruction on 64 bit machine was emulating actual store in
emulate_step() itself until...
Commit be96f63375a1 ("powerpc: Split out instruction analysis part of
emulate_step()"), enabled it for 'stdu' instruction on 64 bit machine.
So kprobe on 'stdu' has always been broken on powerpc64. We haven't
noticed since most stdu operations were probably landing in the red
zone so the exception frame never got corrupted. In that sense, this
fix is needed for BE ever since load/store emulation was added.
For LE, this is only getting exposed now due to my recent patch to
enable load/store emulation on LE, which got merged as commit
e148bd17f48b ("powerpc: Emulation support for load/store instructions
on LE").
Please mark this for stable as well.
Changes in v2:
- Replace 'stwu' with 'stdu' in the comment.
arch/powerpc/kernel/entry_64.S | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/entry_64.S b/arch/powerpc/kernel/entry_64.S
index 6432d4b..767ef6d 100644
--- a/arch/powerpc/kernel/entry_64.S
+++ b/arch/powerpc/kernel/entry_64.S
@@ -689,7 +689,7 @@ resume_kernel:
addi r8,r1,INT_FRAME_SIZE /* Get the kprobed function entry */
- lwz r3,GPR1(r1)
+ ld r3,GPR1(r1)
subi r3,r3,INT_FRAME_SIZE /* dst: Allocate a trampoline exception frame */
mr r4,r1 /* src: current exception frame */
mr r1,r3 /* Reroute the trampoline frame to r1 */
@@ -703,8 +703,8 @@ resume_kernel:
addi r6,r6,8
bdnz 2b
- /* Do real store operation to complete stwu */
- lwz r5,GPR1(r1)
+ /* Do real store operation to complete stdu */
+ ld r5,GPR1(r1)
std r8,0(r5)
/* Clear _TIF_EMULATE_STACK_STORE flag */
--
1.9.3
Powered by blists - more mailing lists