4.4-stable review patch.  If anyone has any objections, please let me know.

------------------

This reverts commit e924c60db1b4891e45d15a33474ac5fab62cf029 which was
commit 7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 upstream.

It shouldn't have been applied as the original was already in 4.4.

Reported-by: Jiri Slaby <jsl...@suse.cz>
Cc: Michael Neuling <mi...@neuling.org>
Cc: Michael Ellerman <m...@ellerman.id.au>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>

---
 arch/powerpc/kernel/process.c |   18 ------------------
 1 file changed, 18 deletions(-)

--- a/arch/powerpc/kernel/process.c
+++ b/arch/powerpc/kernel/process.c
@@ -569,24 +569,6 @@ static void tm_reclaim_thread(struct thr
        if (!MSR_TM_SUSPENDED(mfmsr()))
                return;
 
-       /*
-        * Use the current MSR TM suspended bit to track if we have
-        * checkpointed state outstanding.
-        * On signal delivery, we'd normally reclaim the checkpointed
-        * state to obtain stack pointer (see:get_tm_stackpointer()).
-        * This will then directly return to userspace without going
-        * through __switch_to(). However, if the stack frame is bad,
-        * we need to exit this thread which calls __switch_to() which
-        * will again attempt to reclaim the already saved tm state.
-        * Hence we need to check that we've not already reclaimed
-        * this state.
-        * We do this using the current MSR, rather tracking it in
-        * some specific thread_struct bit, as it has the additional
-        * benifit of checking for a potential TM bad thing exception.
-        */
-       if (!MSR_TM_SUSPENDED(mfmsr()))
-               return;
-
        tm_reclaim(thr, thr->regs->msr, cause);
 
        /* Having done the reclaim, we now have the checkpointed


Reply via email to