Re: [PATCH] powerpc/tm: do not use r13 for tabort_syscall

2016-08-21 Thread Michael Neuling
On Fri, 2016-07-22 at 17:27 +1000, Nicholas Piggin wrote: > tabort_syscall runs with RI=1, so a nested recoverable machine > check will load the paca into r13 and overwrite what we loaded > it with, because exceptions returning to privileged mode do not > restore r13. > > This has survived

[PATCH] powerpc/tm: do not use r13 for tabort_syscall

2016-07-24 Thread Nicholas Piggin
tabort_syscall runs with RI=1, so a nested recoverable machine check will load the paca into r13 and overwrite what we loaded it with, because exceptions returning to privileged mode do not restore r13. Fixes: b4b56f9ecab4 (powerpc/tm: Abort syscalls in active transactions) Cc:

Re: [PATCH] powerpc/tm: do not use r13 for tabort_syscall

2016-07-24 Thread Michael Neuling
On Fri, 2016-07-22 at 17:27 +1000, Nicholas Piggin wrote: > tabort_syscall runs with RI=1, so a nested recoverable machine > check will load the paca into r13 and overwrite what we loaded > it with, because exceptions returning to privileged mode do not > restore r13. > > This has survived

[PATCH] powerpc/tm: do not use r13 for tabort_syscall

2016-07-22 Thread Nicholas Piggin
tabort_syscall runs with RI=1, so a nested recoverable machine check will load the paca into r13 and overwrite what we loaded it with, because exceptions returning to privileged mode do not restore r13. This has survived testing with sc instruction inside transaction (bare sc, not glibc syscall