summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorBreno Leitao <leitao@debian.org>2019-04-08 16:32:38 +1000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-04-17 08:37:43 +0200
commit7f8e322e448b493cab180fe6c85a1cbe9c0c2aad (patch)
tree161844ab7e6e5071456a71e8b51563050c471489 /Makefile
parent3cb115e638ecc8ff0c626e4a227e297afaacf055 (diff)
downloadlinux-stable-7f8e322e448b493cab180fe6c85a1cbe9c0c2aad.tar.gz
linux-stable-7f8e322e448b493cab180fe6c85a1cbe9c0c2aad.tar.bz2
linux-stable-7f8e322e448b493cab180fe6c85a1cbe9c0c2aad.zip
powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM
[ Upstream commit 897bc3df8c5aebb54c32d831f917592e873d0559 ] Commit e1c3743e1a20 ("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: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de> Fixes: e1c3743e1a20 ("powerpc/tm: Set MSR[TS] just prior to recheckpoint") Signed-off-by: Breno Leitao <leitao@debian.org> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions