[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240814033004.2216000-1-yuehaibing@huawei.com>
Date: Wed, 14 Aug 2024 11:30:04 +0800
From: Yue Haibing <yuehaibing@...wei.com>
To: <paul@...l-moore.com>, <jmorris@...ei.org>, <serge@...lyn.com>,
<kees@...nel.org>, <casey@...aufler-ca.com>
CC: <linux-security-module@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<yuehaibing@...wei.com>
Subject: [PATCH -next] lockdown: Make lockdown_lsmid static
Fix sparse warning:
security/lockdown/lockdown.c:79:21: warning:
symbol 'lockdown_lsmid' was not declared. Should it be static?
Signed-off-by: Yue Haibing <yuehaibing@...wei.com>
---
security/lockdown/lockdown.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c
index cd84d8ea1dfb..f2bdbd55aa2b 100644
--- a/security/lockdown/lockdown.c
+++ b/security/lockdown/lockdown.c
@@ -76,7 +76,7 @@ static struct security_hook_list lockdown_hooks[] __ro_after_init = {
LSM_HOOK_INIT(locked_down, lockdown_is_locked_down),
};
-const struct lsm_id lockdown_lsmid = {
+static const struct lsm_id lockdown_lsmid = {
.name = "lockdown",
.id = LSM_ID_LOCKDOWN,
};
--
2.34.1
Powered by blists - more mailing lists