From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Gustavo Romero <gromero@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: stable@vger.kernel.org, mikey@neuling.org, cyrilbur@gmail.com,
sam.bobroff@au1.ibm.com
Subject: Re: [v2] powerpc/tm: Flush TM only if CPU has TM feature
Date: Thu, 21 Sep 2017 11:46:43 +1000 (AEST) [thread overview]
Message-ID: <3xyKGW31PFz9sPk@ozlabs.org> (raw)
In-Reply-To: <1505355228-15039-1-git-send-email-gromero@linux.vnet.ibm.com>
On Thu, 2017-09-14 at 02:13:48 UTC, Gustavo Romero wrote:
> Commit cd63f3c ("powerpc/tm: Fix saving of TM SPRs in core dump")
> added code to access TM SPRs in flush_tmregs_to_thread(). However
> flush_tmregs_to_thread() does not check if TM feature is available on
> CPU before trying to access TM SPRs in order to copy live state to
> thread structures. flush_tmregs_to_thread() is indeed guarded by
> CONFIG_PPC_TRANSACTIONAL_MEM but it might be the case that kernel
> was compiled with CONFIG_PPC_TRANSACTIONAL_MEM enabled and ran on
> a CPU without TM feature available, thus rendering the execution
> of TM instructions that are treated by the CPU as illegal instructions.
>
> The fix is just to add proper checking in flush_tmregs_to_thread()
> if CPU has the TM feature before accessing any TM-specific resource,
> returning immediately if TM is no available on the CPU. Adding
> that checking in flush_tmregs_to_thread() instead of in places
> where it is called, like in vsr_get() and vsr_set(), is better because
> avoids the same problem cropping up elsewhere.
>
> Cc: stable@vger.kernel.org # v4.13+
> Fixes: cd63f3c ("powerpc/tm: Fix saving of TM SPRs in core dump")
> Signed-off-by: Gustavo Romero <gromero@linux.vnet.ibm.com>
> Reviewed-by: Cyril Bur <cyrilbur@gmail.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/c1fa0768a8713b135848f78fd43ffc
cheers
prev parent reply other threads:[~2017-09-21 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 15:10 [PATCH] powerpc/tm: Flush TM only if CPU has TM feature Gustavo Romero
2017-09-14 2:13 ` [PATCH v2] " Gustavo Romero
2017-09-15 1:18 ` Cyril Bur
2017-09-21 1:46 ` Michael Ellerman [this message]
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=3xyKGW31PFz9sPk@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=gromero@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=sam.bobroff@au1.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).