LSM: Refactor "security=" in terms of enable/disable
authorKees Cook <keescook@chromium.org>
Wed, 19 Sep 2018 20:32:15 +0000 (13:32 -0700)
committerKees Cook <keescook@chromium.org>
Tue, 8 Jan 2019 21:18:43 +0000 (13:18 -0800)
commit7e611486d905f435faf80969deed68a615019e6b
tree2454816badf417db4dd7f5005d3c180d0771b4ae
parent5ef4e41918b2dffffa445d8d3a45f3dc257920dc
LSM: Refactor "security=" in terms of enable/disable

For what are marked as the Legacy Major LSMs, make them effectively
exclusive when selected on the "security=" boot parameter, to handle
the future case of when a previously major LSMs become non-exclusive
(e.g. when TOMOYO starts blob-sharing).

Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Casey Schaufler <casey@schaufler-ca.com>
security/security.c