Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Michael Neuling <mikey@neuling.org>
Cc: stable@vger.kernel.org, Fredrik Noring <noring@nocrew.org>,
	Breno Leitao <leitao@debian.org>,
	Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 4.19] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM
Date: Mon, 8 Apr 2019 10:45:52 -0400	[thread overview]
Message-ID: <20190408144552.GF4689@sasha-vm> (raw)
In-Reply-To: <20190408063238.16181-1-mikey@neuling.org>

On Mon, Apr 08, 2019 at 04:32:38PM +1000, Michael Neuling wrote:
>From: Breno Leitao <leitao@debian.org>
>
>commit 897bc3df8c5aebb54c32d831f917592e873d0559 upstream.
>
>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: Michael Neuling <mikey@neuling.org>
>---
>Greg: I think the original patch got rejected with a conflict.
>This correctly applies to v4.19.34.

Thanks for the backport, I've queued it for 4.9-4.19 since the patch it
fixes is included in all of those.

--
Thanks,
Sasha

  reply	other threads:[~2019-04-08 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08  6:32 [PATCH 4.19] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM Michael Neuling
2019-04-08 14:45 ` Sasha Levin [this message]
2019-04-15 16:35   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190408144552.GF4689@sasha-vm \
    --to=sashal@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=mikey@neuling.org \
    --cc=mpe@ellerman.id.au \
    --cc=noring@nocrew.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox