mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 11:11:45 -04:00
x86/mmiotrace: Lock down the testmmiotrace module
The testmmiotrace module shouldn't be permitted when the kernel is locked down as it can be used to arbitrarily read and write MMIO space. This is a runtime check rather than buildtime in order to allow configurations where the same kernel may be run in both locked down or permissive modes depending on local policy. Suggested-by: Thomas Gleixner <[email protected]> Signed-off-by: David Howells <[email protected] Signed-off-by: Matthew Garrett <[email protected]> Acked-by: Steven Rostedt (VMware) <[email protected]> Reviewed-by: Kees Cook <[email protected]> cc: Thomas Gleixner <[email protected]> cc: Steven Rostedt <[email protected]> cc: Ingo Molnar <[email protected]> cc: "H. Peter Anvin" <[email protected]> cc: [email protected] Signed-off-by: James Morris <[email protected]>
This commit is contained in:
parent
20657f66ef
commit
906357f77a
3 changed files with 7 additions and 0 deletions
|
|
@ -29,6 +29,7 @@ static char *lockdown_reasons[LOCKDOWN_CONFIDENTIALITY_MAX+1] = {
|
|||
[LOCKDOWN_PCMCIA_CIS] = "direct PCMCIA CIS storage",
|
||||
[LOCKDOWN_TIOCSSERIAL] = "reconfiguration of serial port IO",
|
||||
[LOCKDOWN_MODULE_PARAMETERS] = "unsafe module parameters",
|
||||
[LOCKDOWN_MMIOTRACE] = "unsafe mmio",
|
||||
[LOCKDOWN_INTEGRITY_MAX] = "integrity",
|
||||
[LOCKDOWN_CONFIDENTIALITY_MAX] = "confidentiality",
|
||||
};
|
||||
|
|
|
|||
Loading…
Reference in a new issue