Re: [RFC PATCH 24/29] lockdown: move initcalls to the LSM framework
From: John Johansen <john.johansen@canonical.com>
Date: 2025-05-14 13:31:29
Also in:
linux-integrity, selinux
On 4/9/25 11:50, Paul Moore wrote:
Signed-off-by: Paul Moore <paul@paul-moore.com>
Reviewed-by: John Johansen <john.johansen@canonical.com>
quoted hunk ↗ jump to hunk
--- security/lockdown/lockdown.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c index 4813f168ff93..8d46886d2cca 100644 --- a/security/lockdown/lockdown.c +++ b/security/lockdown/lockdown.c@@ -161,8 +161,6 @@ static int __init lockdown_secfs_init(void) return PTR_ERR_OR_ZERO(dentry); } -core_initcall(lockdown_secfs_init); - #ifdef CONFIG_SECURITY_LOCKDOWN_LSM_EARLY DEFINE_EARLY_LSM(lockdown) = { #else@@ -170,4 +168,5 @@ DEFINE_LSM(lockdown) = { #endif .id = &lockdown_lsmid, .init = lockdown_lsm_init, + .initcall_core = lockdown_secfs_init, };