summaryrefslogtreecommitdiffstats
path: root/drivers/usb/core/urb.c
diff options
context:
space:
mode:
authorMichael Ellerman <mpe@ellerman.id.au>2019-02-22 13:22:08 +1100
committerMichael Ellerman <mpe@ellerman.id.au>2019-02-22 13:41:13 +1100
commitc3c7470c75566a077c8dc71dcf8f1948b8ddfab4 (patch)
tree7600bc038316c979526f3e74e2c52cb5292b84c5 /drivers/usb/core/urb.c
parentc05772018491e5294f55d63b239ab0d532e96616 (diff)
downloadlinux-c3c7470c75566a077c8dc71dcf8f1948b8ddfab4.tar.bz2
powerpc/kvm: Save and restore host AMR/IAMR/UAMOR
When the hash MMU is active the AMR, IAMR and UAMOR are used for pkeys. The AMR is directly writable by user space, and the UAMOR masks those writes, meaning both registers are effectively user register state. The IAMR is used to create an execute only key. Also we must maintain the value of at least the AMR when running in process context, so that any memory accesses done by the kernel on behalf of the process are correctly controlled by the AMR. Although we are correctly switching all registers when going into a guest, on returning to the host we just write 0 into all regs, except on Power9 where we restore the IAMR correctly. This could be observed by a user process if it writes the AMR, then runs a guest and we then return immediately to it without rescheduling. Because we have written 0 to the AMR that would have the effect of granting read/write permission to pages that the process was trying to protect. In addition, when using the Radix MMU, the AMR can prevent inadvertent kernel access to userspace data, writing 0 to the AMR disables that protection. So save and restore AMR, IAMR and UAMOR. Fixes: cf43d3b26452 ("powerpc: Enable pkey subsystem") Cc: stable@vger.kernel.org # v4.16+ Signed-off-by: Russell Currey <ruscur@russell.cc> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Acked-by: Paul Mackerras <paulus@ozlabs.org>
Diffstat (limited to 'drivers/usb/core/urb.c')
0 files changed, 0 insertions, 0 deletions