summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorMichael Neuling <mikey@neuling.org>2013-06-09 21:23:17 +1000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2013-06-20 17:05:22 +1000
commit2c27a18f8736da047bef2b997bdd48efc667e3c9 (patch)
tree682bf6a75cf71f455b31f920bb40e7b846794661 /crypto
parentfee55450710dff32a13ae30b4129ec7b5a4b44d0 (diff)
downloadop-kernel-dev-2c27a18f8736da047bef2b997bdd48efc667e3c9.zip
op-kernel-dev-2c27a18f8736da047bef2b997bdd48efc667e3c9.tar.gz
powerpc/tm: Fix restoration of MSR on 32bit signal return
Currently we clear out the MSR TM bits on signal return assuming that the signal should never return to an active transaction. This is bogus as the user may do this. It's most likely the transaction will be doomed due to a treclaim but that's a problem for the HW not the kernel. The current code is a legacy of earlier kernel implementations which did software rollback of active transactions in the kernel. That code has now gone but we didn't correctly fix up this part of the signals code which still makes the assumption that it must be returning to a suspended transaction. This pulls out both MSR TM bits from the user supplied context rather than just setting TM suspend. We pull out only the bits needed to ensure the user can't do anything dangerous to the MSR. Signed-off-by: Michael Neuling <mikey@neuling.org> cc: stable@vger.kernel.org (v3.9+) Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud