aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/fault-injection
diff options
context:
space:
mode:
authorMichael Neuling <mikey@neuling.org>2018-09-25 19:36:47 +1000
committerMichael Ellerman <mpe@ellerman.id.au>2018-09-25 22:51:32 +1000
commit96dc89d526ef77604376f06220e3d2931a0bfd58 (patch)
treef0654ed863e42de110a65900fdfaf2e82c10fb3e /tools/testing/fault-injection
parentpowerpc/tm: Fix userspace r13 corruption (diff)
downloadlinux-dev-96dc89d526ef77604376f06220e3d2931a0bfd58.tar.xz
linux-dev-96dc89d526ef77604376f06220e3d2931a0bfd58.zip
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>
Diffstat (limited to 'tools/testing/fault-injection')
0 files changed, 0 insertions, 0 deletions