diff options
| author | Casey Schaufler <casey@schaufler-ca.com> | 2017-01-18 17:09:05 -0800 |
|---|---|---|
| committer | James Morris <james.l.morris@oracle.com> | 2017-01-19 13:18:29 +1100 |
| commit | d69dece5f5b6bc7a5e39d2b6136ddc69469331fe (patch) | |
| tree | b4c23177baf246a1f64b83442fc3359cbc0d8f38 /security/tomoyo/tomoyo.c | |
| parent | 3ccb76c5dfe0d25c1d0168d5b726d0b43d19a485 (diff) | |
| download | linux-d69dece5f5b6bc7a5e39d2b6136ddc69469331fe.tar.gz linux-d69dece5f5b6bc7a5e39d2b6136ddc69469331fe.tar.bz2 linux-d69dece5f5b6bc7a5e39d2b6136ddc69469331fe.zip | |
LSM: Add /sys/kernel/security/lsm
I am still tired of having to find indirect ways to determine
what security modules are active on a system. I have added
/sys/kernel/security/lsm, which contains a comma separated
list of the active security modules. No more groping around
in /proc/filesystems or other clever hacks.
Unchanged from previous versions except for being updated
to the latest security next branch.
Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Acked-by: John Johansen <john.johansen@canonical.com>
Acked-by: Paul Moore <paul@paul-moore.com>
Acked-by: Kees Cook <keescook@chromium.org>
Signed-off-by: James Morris <james.l.morris@oracle.com>
Diffstat (limited to 'security/tomoyo/tomoyo.c')
| -rw-r--r-- | security/tomoyo/tomoyo.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/security/tomoyo/tomoyo.c b/security/tomoyo/tomoyo.c index 75c998700190..edc52d620f29 100644 --- a/security/tomoyo/tomoyo.c +++ b/security/tomoyo/tomoyo.c @@ -542,7 +542,7 @@ static int __init tomoyo_init(void) if (!security_module_enable("tomoyo")) return 0; /* register ourselves with the security framework */ - security_add_hooks(tomoyo_hooks, ARRAY_SIZE(tomoyo_hooks)); + security_add_hooks(tomoyo_hooks, ARRAY_SIZE(tomoyo_hooks), "tomoyo"); printk(KERN_INFO "TOMOYO Linux initialized\n"); cred->security = &tomoyo_kernel_domain; tomoyo_mm_init(); |