mirror of
https://github.com/Kicksecure/security-misc.git
synced 2025-11-25 15:28:08 -05:00
Improve clarity for panic on OOM
This commit is contained in:
parent
b89aaea61e
commit
0b9b9ffb1e
1 changed files with 2 additions and 1 deletions
|
|
@ -201,7 +201,6 @@ kernel.perf_event_paranoid=3
|
|||
|
||||
## Force immediate kernel panic on OOM (out of memory) scenarios.
|
||||
## Registers a kernel panic whenever the oom_killer is triggered to kill some rouge process based on their OOM score.
|
||||
## Note that this must be used with kernel.panic=-1 for it to be function as intended.
|
||||
## This prevents security features such as the screen locker, kloak, and emerg-shutdown from being arbitrarily terminated.
|
||||
## Enabling these two together creates a risk of userspace-based denial-of-service attacks that maliciously fill memory.
|
||||
## This forces immediate system reboot rather than placing any reliance on the oom_killer.
|
||||
|
|
@ -213,6 +212,8 @@ kernel.perf_event_paranoid=3
|
|||
## https://github.com/KSPP/kspp.github.io/issues/9
|
||||
## https://github.com/Kicksecure/security-misc/issues/324
|
||||
##
|
||||
## Note that this must be used with kernel.panic=-1 for it to function as intended.
|
||||
##
|
||||
#vm.panic_on_oom=2
|
||||
|
||||
## Disable the use of legacy TIOCSTI operations which can be used to inject keypresses.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue