Skip to content

Commit 96dc89d

Browse files
mikeympe
authored andcommitted
powerpc/tm: Avoid possible userspace r1 corruption on reclaim
Current we store the userspace r1 to PACATMSCRATCH before finally saving it to the thread struct. In theory an exception could be taken here (like a machine check or SLB miss) that could write PACATMSCRATCH and hence corrupt the userspace r1. The SLB fault currently doesn't touch PACATMSCRATCH, but others do. We've never actually seen this happen but it's theoretically possible. Either way, the code is fragile as it is. This patch saves r1 to the kernel stack (which can't fault) before we turn MSR[RI] back on. PACATMSCRATCH is still used but only with MSR[RI] off. We then copy r1 from the kernel stack to the thread struct once we have MSR[RI] back on. Suggested-by: Breno Leitao <leitao@debian.org> Signed-off-by: Michael Neuling <mikey@neuling.org> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
1 parent cf13435 commit 96dc89d

File tree

1 file changed

+8
-1
lines changed
  • arch/powerpc/kernel

1 file changed

+8
-1
lines changed

arch/powerpc/kernel/tm.S

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,6 +178,13 @@ _GLOBAL(tm_reclaim)
178178

179179
std r11, GPR11(r1) /* Temporary stash */
180180

181+
/*
182+
* Move the saved user r1 to the kernel stack in case PACATMSCRATCH is
183+
* clobbered by an exception once we turn on MSR_RI below.
184+
*/
185+
ld r11, PACATMSCRATCH(r13)
186+
std r11, GPR1(r1)
187+
181188
/*
182189
* Store r13 away so we can free up the scratch SPR for the SLB fault
183190
* handler (needed once we start accessing the thread_struct).
@@ -214,7 +221,7 @@ _GLOBAL(tm_reclaim)
214221
SAVE_GPR(8, r7) /* user r8 */
215222
SAVE_GPR(9, r7) /* user r9 */
216223
SAVE_GPR(10, r7) /* user r10 */
217-
ld r3, PACATMSCRATCH(r13) /* user r1 */
224+
ld r3, GPR1(r1) /* user r1 */
218225
ld r4, GPR7(r1) /* user r7 */
219226
ld r5, GPR11(r1) /* user r11 */
220227
ld r6, GPR12(r1) /* user r12 */

0 commit comments

Comments
 (0)