diff options
author | Christophe Leroy <christophe.leroy@csgroup.eu> | 2021-10-19 09:29:28 +0200 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2021-12-09 22:41:19 +1100 |
commit | 43afcf8f0101279cf4243bb4f9f9b249ddd8613c (patch) | |
tree | 84c7009b86ba5685407f7ed3afe1b397c26f1233 /arch/powerpc/kernel/firmware.c | |
parent | e3c02f25b4296c48376b8edb6aadcec460e803bc (diff) | |
download | linux-stable-43afcf8f0101279cf4243bb4f9f9b249ddd8613c.tar.gz linux-stable-43afcf8f0101279cf4243bb4f9f9b249ddd8613c.tar.bz2 linux-stable-43afcf8f0101279cf4243bb4f9f9b249ddd8613c.zip |
powerpc: Add KUAP support for BOOKE and 40x
On booke/40x we don't have segments like book3s/32.
On booke/40x we don't have access protection groups like 8xx.
Use the PID register to provide user access protection.
Kernel address space can be accessed with any PID.
User address space has to be accessed with the PID of the user.
User PID is always not null.
Everytime the kernel is entered, set PID register to 0 and
restore PID register when returning to user.
Everytime kernel needs to access user data, PID is restored
for the access.
In TLB miss handlers, check the PID and bail out to data storage
exception when PID is 0 and accessed address is in user space.
Note that also forbids execution of user text by kernel except
when user access is unlocked. But this shouldn't be a problem
as the kernel is not supposed to ever run user text.
This patch prepares the infrastructure but the real activation of KUAP
is done by following patches for each processor type one by one.
Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/5d65576a8e31e9480415785a180c92dd4e72306d.1634627931.git.christophe.leroy@csgroup.eu
Diffstat (limited to 'arch/powerpc/kernel/firmware.c')
0 files changed, 0 insertions, 0 deletions