From: Paul Moore <paul@paul-moore.com>
To: linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org, selinux@vger.kernel.org
Cc: "John Johansen" <john.johansen@canonical.com>,
"Mimi Zohar" <zohar@linux.ibm.com>,
"Roberto Sassu" <roberto.sassu@huawei.com>,
"Fan Wu" <wufan@kernel.org>, "Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack@google.com>,
"Kees Cook" <kees@kernel.org>,
"Micah Morton" <mortonm@chromium.org>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"Tetsuo Handa" <penguin-kernel@I-love.SAKURA.ne.jp>,
"Nicolas Bouchinet" <nicolas.bouchinet@oss.cyber.gouv.fr>,
"Xiu Jianfeng" <xiujianfeng@huawei.com>
Subject: [PATCH v3 19/34] lsm: add/tweak function header comment blocks in lsm_init.c
Date: Thu, 14 Aug 2025 18:50:28 -0400 [thread overview]
Message-ID: <20250814225159.275901-55-paul@paul-moore.com> (raw)
In-Reply-To: <20250814225159.275901-36-paul@paul-moore.com>
Add function header comments for lsm_static_call_init() and
early_security_init(), tweak the existing comment block for
security_add_hooks().
Reviewed-by: Casey Schaufler <casey@schaufler-ca.com>
Signed-off-by: Paul Moore <paul@paul-moore.com>
---
security/lsm_init.c | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/security/lsm_init.c b/security/lsm_init.c
index f87f5441617b..37593805ba9e 100644
--- a/security/lsm_init.c
+++ b/security/lsm_init.c
@@ -315,6 +315,10 @@ static void __init lsm_order_parse(const char *list, const char *src)
}
}
+/**
+ * lsm_static_call_init - Initialize a LSM's static calls
+ * @hl: LSM hook list
+ */
static void __init lsm_static_call_init(struct security_hook_list *hl)
{
struct lsm_static_call *scall = hl->scalls;
@@ -335,12 +339,12 @@ static void __init lsm_static_call_init(struct security_hook_list *hl)
}
/**
- * security_add_hooks - Add a modules hooks to the hook lists.
- * @hooks: the hooks to add
- * @count: the number of hooks to add
- * @lsmid: the identification information for the security module
+ * security_add_hooks - Add a LSM's hooks to the LSM framework's hook lists
+ * @hooks: LSM hooks to add
+ * @count: number of hooks to add
+ * @lsmid: identification information for the LSM
*
- * Each LSM has to register its hooks with the infrastructure.
+ * Each LSM has to register its hooks with the LSM framework.
*/
void __init security_add_hooks(struct security_hook_list *hooks, int count,
const struct lsm_id *lsmid)
@@ -353,6 +357,9 @@ void __init security_add_hooks(struct security_hook_list *hooks, int count,
}
}
+/**
+ * early_security_init - Initialize the early LSMs
+ */
int __init early_security_init(void)
{
struct lsm_info *lsm;
--
2.50.1
next prev parent reply other threads:[~2025-08-14 22:54 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 22:50 [RFC PATCH v3 0/34] Rework the LSM initialization Paul Moore
2025-08-14 22:50 ` [PATCH v3 01/34] lsm: split the notifier code out into lsm_notifier.c Paul Moore
2025-08-14 22:50 ` [PATCH v3 02/34] lsm: split the init code out into lsm_init.c Paul Moore
2025-08-14 22:50 ` [PATCH v3 03/34] lsm: consolidate lsm_allowed() and prepare_lsm() into lsm_prepare() Paul Moore
2025-09-02 16:33 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 04/34] lsm: introduce looping macros for the initialization code Paul Moore
2025-09-02 16:37 ` John Johansen
2025-09-03 20:07 ` Paul Moore
2025-08-14 22:50 ` [PATCH v3 05/34] lsm: integrate report_lsm_order() code into caller Paul Moore
2025-09-02 16:53 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 06/34] lsm: integrate lsm_early_cred() and lsm_early_task() " Paul Moore
2025-09-02 16:55 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 07/34] lsm: rename ordered_lsm_init() to lsm_init_ordered() Paul Moore
2025-09-02 16:56 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 08/34] lsm: replace the name field with a pointer to the lsm_id struct Paul Moore
2025-08-14 22:50 ` [PATCH v3 09/34] lsm: rename the lsm order variables for consistency Paul Moore
2025-08-14 22:50 ` [PATCH v3 10/34] lsm: rework lsm_active_cnt and lsm_idlist[] Paul Moore
2025-09-02 17:01 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 11/34] lsm: get rid of the lsm_names list and do some cleanup Paul Moore
2025-08-15 17:00 ` Casey Schaufler
2025-09-02 17:20 ` John Johansen
2025-09-03 20:26 ` Paul Moore
2025-09-03 23:12 ` John Johansen
2025-09-04 8:12 ` Roberto Sassu
2025-09-04 8:48 ` John Johansen
2025-09-04 15:18 ` Paul Moore
2025-09-04 17:52 ` Paul Moore
2025-08-14 22:50 ` [PATCH v3 12/34] lsm: rework the LSM enable/disable setter/getter functions Paul Moore
2025-09-02 17:39 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 13/34] lsm: rename exists_ordered_lsm() to lsm_order_exists() Paul Moore
2025-09-02 17:42 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 14/34] lsm: rename/rework append_ordered_lsm() into lsm_order_append() Paul Moore
2025-09-03 0:17 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 15/34] lsm: rename/rework ordered_lsm_parse() to lsm_order_parse() Paul Moore
2025-09-03 8:40 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 16/34] lsm: cleanup the LSM blob size code Paul Moore
2025-08-14 22:50 ` [PATCH v3 17/34] lsm: cleanup initialize_lsm() and rename to lsm_init_single() Paul Moore
2025-08-15 17:05 ` Casey Schaufler
2025-08-14 22:50 ` [PATCH v3 18/34] lsm: fold lsm_init_ordered() into security_init() Paul Moore
2025-09-03 8:47 ` John Johansen
2025-08-14 22:50 ` Paul Moore [this message]
2025-09-03 8:48 ` [PATCH v3 19/34] lsm: add/tweak function header comment blocks in lsm_init.c John Johansen
2025-08-14 22:50 ` [PATCH v3 20/34] lsm: cleanup the debug and console output " Paul Moore
2025-09-03 10:22 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 21/34] lsm: output available LSMs when debugging Paul Moore
2025-09-03 8:49 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 22/34] lsm: group lsm_order_parse() with the other lsm_order_*() functions Paul Moore
2025-09-02 17:46 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 23/34] lsm: introduce an initcall mechanism into the LSM framework Paul Moore
2025-09-02 17:50 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 24/34] loadpin: move initcalls to " Paul Moore
2025-09-02 17:51 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 25/34] ipe: " Paul Moore
2025-09-02 17:52 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 26/34] smack: " Paul Moore
2025-09-02 18:08 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 27/34] tomoyo: " Paul Moore
2025-09-02 18:09 ` John Johansen
2025-09-03 20:32 ` Paul Moore
2025-09-04 9:52 ` Tetsuo Handa
2025-09-04 15:02 ` Paul Moore
2025-08-14 22:50 ` [PATCH v3 28/34] safesetid: " Paul Moore
2025-09-02 18:10 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 29/34] apparmor: " Paul Moore
2025-09-03 20:34 ` Paul Moore
2025-09-03 23:15 ` John Johansen
2025-09-04 1:28 ` Paul Moore
2025-08-14 22:50 ` [PATCH v3 30/34] lockdown: " Paul Moore
2025-09-02 18:12 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 31/34] ima,evm: " Paul Moore
2025-08-22 20:45 ` Paul Moore
2025-09-02 12:50 ` Roberto Sassu
2025-09-02 12:54 ` [PATCH] " Roberto Sassu
2025-09-03 20:43 ` Paul Moore
2025-08-14 22:50 ` [PATCH v3 32/34] selinux: " Paul Moore
2025-08-14 22:50 ` [PATCH v3 33/34] lsm: consolidate all of the LSM framework initcalls Paul Moore
2025-09-02 18:20 ` John Johansen
2025-08-14 22:50 ` [PATCH v3 34/34] lsm: add a LSM_STARTED_ALL notification event Paul Moore
2025-09-02 18:21 ` John Johansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250814225159.275901-55-paul@paul-moore.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=gnoack@google.com \
--cc=john.johansen@canonical.com \
--cc=kees@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mortonm@chromium.org \
--cc=nicolas.bouchinet@oss.cyber.gouv.fr \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=roberto.sassu@huawei.com \
--cc=selinux@vger.kernel.org \
--cc=wufan@kernel.org \
--cc=xiujianfeng@huawei.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).