Re: [RFC PATCH v2 30/34] lockdown: move initcalls to the LSM framework

[xiujianfeng]

On 2025/7/26 0:51, Paul Moore wrote:
> On Fri, Jul 25, 2025 at 4:12 AM Xiu Jianfeng
> <xiujianf...@huaweicloud.com> wrote:
>> On 2025/7/22 7:21, Paul Moore wrote:
>>> Reviewed-by: Kees Cook <k...@kernel.org>
>>> Signed-off-by: Paul Moore <p...@paul-moore.com>
>>
>> Reviewed-by: Xiu Jianfeng <xiujianf...@huawei.com>
> 
> Thank you for reviewing this patch.  As you are a Lockdown maintainer,
> can I change your reviewed-by into an acked-by tag?

Yes, absolutely! Thanks for checking!

> 
>>> ---
>>>  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,
>>>  };
>