diff options
| author | Lincoln Wallace <locnnil0@gmail.com> | 2026-07-13 22:38:31 -0300 |
|---|---|---|
| committer | Paul Moore <paul@paul-moore.com> | 2026-09-11 18:09:29 -0400 |
| commit | 5a06263597a8b7b528d92999cf654667f61d92a7 (patch) | |
| tree | 309591be6e535a27f4bb304f4ee3245868afe63a /scripts/Makefile.thinlto | |
| parent | ed578004b26b49325abc5ad84bcc33a82e76f602 (diff) | |
| download | linux-5a06263597a8b7b528d92999cf654667f61d92a7.tar.gz linux-5a06263597a8b7b528d92999cf654667f61d92a7.zip | |
doc: describe CONFIG_LSM and lsm= as the selection mechanism
The LSM usage document states that security modules are selectable at
build time via CONFIG_DEFAULT_SECURITY and can be overridden at boot
time via the "security=..." kernel command line argument.
CONFIG_DEFAULT_SECURITY no longer exists: LSMs are enabled via
CONFIG_LSM, an ordered list of the LSMs to initialize, which can be
overridden at boot time with the "lsm=" parameter. The "security="
parameter remains as a deprecated way to choose a legacy "major"
security module, and is ignored when "lsm=" is specified; see commit
89a9684ea158 ("LSM: Ignore "security=" when "lsm=" is specified").
Update the paragraph to describe CONFIG_LSM and "lsm=" as the current
selection mechanism, keeping "security=" documented as the deprecated
legacy option, matching the wording in kernel-parameters.txt.
Signed-off-by: Lincoln Wallace <locnnil0@gmail.com>
[PM: subject tweak, dropped refs to earlier rejected revisions]
Signed-off-by: Paul Moore <paul@paul-moore.com>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
