Commit 897bc3df authored by Breno Leitao's avatar Breno Leitao Committed by Michael Ellerman

powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM

Commit e1c3743e ("powerpc/tm: Set MSR[TS] just prior to recheckpoint")
moved a code block around and this block uses a 'msr' variable outside of
the CONFIG_PPC_TRANSACTIONAL_MEM, however the 'msr' variable is declared
inside a CONFIG_PPC_TRANSACTIONAL_MEM block, causing a possible error when
CONFIG_PPC_TRANSACTION_MEM is not defined.

	error: 'msr' undeclared (first use in this function)

This is not causing a compilation error in the mainline kernel, because
'msr' is being used as an argument of MSR_TM_ACTIVE(), which is defined as
the following when CONFIG_PPC_TRANSACTIONAL_MEM is *not* set:

	#define MSR_TM_ACTIVE(x) 0

This patch just fixes this issue avoiding the 'msr' variable usage outside
the CONFIG_PPC_TRANSACTIONAL_MEM block, avoiding trusting in the
MSR_TM_ACTIVE() definition.

Cc: stable@vger.kernel.org
Reported-by: default avatarChristoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Fixes: e1c3743e ("powerpc/tm: Set MSR[TS] just prior to recheckpoint")
Signed-off-by: default avatarBreno Leitao <leitao@debian.org>
Signed-off-by: default avatarMichael Ellerman <mpe@ellerman.id.au>
parent fb0bdec5
...@@ -755,11 +755,12 @@ SYSCALL_DEFINE0(rt_sigreturn) ...@@ -755,11 +755,12 @@ SYSCALL_DEFINE0(rt_sigreturn)
if (restore_tm_sigcontexts(current, &uc->uc_mcontext, if (restore_tm_sigcontexts(current, &uc->uc_mcontext,
&uc_transact->uc_mcontext)) &uc_transact->uc_mcontext))
goto badframe; goto badframe;
} } else
#endif #endif
/* Fall through, for non-TM restore */ {
if (!MSR_TM_ACTIVE(msr)) {
/* /*
* Fall through, for non-TM restore
*
* Unset MSR[TS] on the thread regs since MSR from user * Unset MSR[TS] on the thread regs since MSR from user
* context does not have MSR active, and recheckpoint was * context does not have MSR active, and recheckpoint was
* not called since restore_tm_sigcontexts() was not called * not called since restore_tm_sigcontexts() was not called
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment