summaryrefslogtreecommitdiffstats
path: root/arch/s390
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2018-09-24 14:43:59 -0700
committerKees Cook <keescook@chromium.org>2018-10-18 15:29:44 -0700
commit13523bef1e2154b6d02836cd0f6c0ffc89b2eae6 (patch)
treeeb769876befa1a7c81ed78748d9ccc0d3ec46501 /arch/s390
parentf4b626d6de15149329332796e96709e0c4c84577 (diff)
downloadlinux-stable-13523bef1e2154b6d02836cd0f6c0ffc89b2eae6.tar.gz
linux-stable-13523bef1e2154b6d02836cd0f6c0ffc89b2eae6.tar.bz2
linux-stable-13523bef1e2154b6d02836cd0f6c0ffc89b2eae6.zip
LoadPin: Rename boot param "enabled" to "enforce"
LoadPin's "enabled" setting is really about enforcement, not whether or not the LSM is using LSM hooks. Instead, split this out so that LSM enabling can be logically distinct from whether enforcement is happening (for example, the pinning happens when the LSM is enabled, but the pin is only checked when "enforce" is set). This allows LoadPin to continue to operate sanely in test environments once LSM enable/disable is centrally handled (i.e. we want LoadPin to be enabled separately from its enforcement). Signed-off-by: Kees Cook <keescook@chromium.org> Reviewed-by: Casey Schaufler <casey@schaufler-ca.com> Reviewed-by: John Johansen <john.johansen@canonical.com>
Diffstat (limited to 'arch/s390')
0 files changed, 0 insertions, 0 deletions