[PATCH security-next v4 01/32] LSM: Correctly announce start of LSM initialization

Kees Cook keescook at chromium.org
Tue Oct 2 00:54:34 UTC 2018

For a while now, the LSM core has said it was "initializED", rather than
"initializING". This adjust the report to be more accurate (i.e. before
this was reported before any LSMs had been initialized.)

Signed-off-by: Kees Cook <keescook at chromium.org>
Reviewed-by: Casey Schaufler <casey at schaufler-ca.com>
Reviewed-by: James Morris <james.morris at microsoft.com>
Reviewed-by: John Johansen <john.johansen at canonical.com>
 security/security.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/security/security.c b/security/security.c
index 736e78da1ab9..4cbcf244a965 100644
--- a/security/security.c
+++ b/security/security.c
@@ -72,10 +72,11 @@ int __init security_init(void)
 	int i;
 	struct hlist_head *list = (struct hlist_head *) &security_hook_heads;
+	pr_info("Security Framework initializing\n");
 	for (i = 0; i < sizeof(security_hook_heads) / sizeof(struct hlist_head);
-	pr_info("Security Framework initialized\n");
 	 * Load minor LSMs, with the capability module always first.

More information about the Linux-security-module-archive mailing list