From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: Paul Moore <paul@paul-moore.com>,
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: Re: [RFC PATCH v2 26/34] smack: move initcalls to the LSM framework
Date: Mon, 28 Jul 2025 11:46:02 +0200 [thread overview]
Message-ID: <5ff016adea8969e4a97387d4ed88a172bdc4b3de.camel@huaweicloud.com> (raw)
In-Reply-To: <20250721232142.77224-62-paul@paul-moore.com>
On Mon, 2025-07-21 at 19:21 -0400, Paul Moore wrote:
> As the LSM framework only supports one LSM initcall callback for each
> initcall type, the init_smk_fs() and smack_nf_ip_init() functions were
> wrapped with a new function, smack_initcall() that is registered with
> the LSM framework.
>
> Signed-off-by: Paul Moore <paul@paul-moore.com>
> ---
> security/smack/smack.h | 7 +++++++
> security/smack/smack_lsm.c | 9 +++++++++
> security/smack/smack_netfilter.c | 4 +---
> security/smack/smackfs.c | 4 +---
> 4 files changed, 18 insertions(+), 6 deletions(-)
>
> diff --git a/security/smack/smack.h b/security/smack/smack.h
> index bf6a6ed3946c..885a2f2929fd 100644
> --- a/security/smack/smack.h
> +++ b/security/smack/smack.h
> @@ -275,6 +275,13 @@ struct smk_audit_info {
> #endif
> };
>
> +/*
> + * Initialization
> + */
> +int init_smk_fs(void);
> +int smack_nf_ip_init(void);
I made the following changes (due to not having
CONFIG_SECURITY_SMACK_NETFILTER):
diff --git a/security/smack/smack.h b/security/smack/smack.h
index 885a2f2929fd..4401cee2bbb7 100644
--- a/security/smack/smack.h
+++ b/security/smack/smack.h
@@ -279,9 +279,17 @@ struct smk_audit_info {
* Initialization
*/
int init_smk_fs(void);
-int smack_nf_ip_init(void);
int smack_initcall(void);
+#ifdef CONFIG_SECURITY_SMACK_NETFILTER
+int smack_nf_ip_init(void);
+#else
+static inline int smack_nf_ip_init(void)
+{
+ return 0;
+}
+#endif
+
Roberto
> +int smack_initcall(void);
> +
> /*
> * These functions are in smack_access.c
> */
> diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c
> index e09490c75f59..f14d536c516b 100644
> --- a/security/smack/smack_lsm.c
> +++ b/security/smack/smack_lsm.c
> @@ -5270,6 +5270,14 @@ static __init int smack_init(void)
> return 0;
> }
>
> +int __init smack_initcall(void)
> +{
> + int rc_fs = init_smk_fs();
> + int rc_nf = smack_nf_ip_init();
> +
> + return rc_fs ? rc_fs : rc_nf;
> +}
> +
> /*
> * Smack requires early initialization in order to label
> * all processes and objects when they are created.
> @@ -5279,4 +5287,5 @@ DEFINE_LSM(smack) = {
> .flags = LSM_FLAG_LEGACY_MAJOR | LSM_FLAG_EXCLUSIVE,
> .blobs = &smack_blob_sizes,
> .init = smack_init,
> + .initcall_device = smack_initcall,
> };
> diff --git a/security/smack/smack_netfilter.c b/security/smack/smack_netfilter.c
> index 8fd747b3653a..17ba578b1308 100644
> --- a/security/smack/smack_netfilter.c
> +++ b/security/smack/smack_netfilter.c
> @@ -68,7 +68,7 @@ static struct pernet_operations smack_net_ops = {
> .exit = smack_nf_unregister,
> };
>
> -static int __init smack_nf_ip_init(void)
> +int __init smack_nf_ip_init(void)
> {
> if (smack_enabled == 0)
> return 0;
> @@ -76,5 +76,3 @@ static int __init smack_nf_ip_init(void)
> printk(KERN_DEBUG "Smack: Registering netfilter hooks\n");
> return register_pernet_subsys(&smack_net_ops);
> }
> -
> -__initcall(smack_nf_ip_init);
> diff --git a/security/smack/smackfs.c b/security/smack/smackfs.c
> index b1e5e62f5cbd..405ace6db109 100644
> --- a/security/smack/smackfs.c
> +++ b/security/smack/smackfs.c
> @@ -2978,7 +2978,7 @@ static struct vfsmount *smackfs_mount;
> * Returns true if we were not chosen on boot or if
> * we were chosen and filesystem registration succeeded.
> */
> -static int __init init_smk_fs(void)
> +int __init init_smk_fs(void)
> {
> int err;
> int rc;
> @@ -3021,5 +3021,3 @@ static int __init init_smk_fs(void)
>
> return err;
> }
> -
> -__initcall(init_smk_fs);
next prev parent reply other threads:[~2025-07-28 9:46 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 23:21 [RFC PATCH v2 0/34] Rework the LSM initialization Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 01/34] lsm: split the notifier code out into lsm_notifier.c Paul Moore
2025-07-24 14:49 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 02/34] lsm: split the init code out into lsm_init.c Paul Moore
2025-07-24 14:50 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 03/34] lsm: consolidate lsm_allowed() and prepare_lsm() into lsm_prepare() Paul Moore
2025-07-24 14:52 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 04/34] lsm: introduce looping macros for the initialization code Paul Moore
2025-07-24 15:10 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 05/34] lsm: integrate report_lsm_order() code into caller Paul Moore
2025-07-24 15:19 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 06/34] lsm: integrate lsm_early_cred() and lsm_early_task() " Paul Moore
2025-07-24 15:20 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 07/34] lsm: rename ordered_lsm_init() to lsm_init_ordered() Paul Moore
2025-07-24 15:28 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 08/34] lsm: replace the name field with a pointer to the lsm_id struct Paul Moore
2025-07-24 15:30 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 09/34] lsm: rename the lsm order variables for consistency Paul Moore
2025-07-24 15:31 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 10/34] lsm: rework lsm_active_cnt and lsm_idlist[] Paul Moore
2025-07-24 15:34 ` Casey Schaufler
2025-07-25 0:26 ` Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 11/34] lsm: get rid of the lsm_names list and do some cleanup Paul Moore
2025-07-24 15:39 ` Casey Schaufler
2025-07-25 2:28 ` Paul Moore
2025-07-25 14:26 ` Casey Schaufler
2025-07-25 16:42 ` Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 12/34] lsm: rework the LSM enable/disable setter/getter functions Paul Moore
2025-07-24 15:44 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 13/34] lsm: rename exists_ordered_lsm() to lsm_order_exists() Paul Moore
2025-07-24 15:45 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 14/34] lsm: rename/rework append_ordered_lsm() into lsm_order_append() Paul Moore
2025-07-24 15:47 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 15/34] lsm: rename/rework ordered_lsm_parse() to lsm_order_parse() Paul Moore
2025-07-24 15:48 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 16/34] lsm: cleanup the LSM blob size code Paul Moore
2025-07-24 23:28 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 17/34] lsm: cleanup initialize_lsm() and rename to lsm_init_single() Paul Moore
2025-07-24 23:29 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 18/34] lsm: fold lsm_init_ordered() into security_init() Paul Moore
2025-07-24 23:30 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 19/34] lsm: add/tweak function header comment blocks in lsm_init.c Paul Moore
2025-07-24 23:31 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 20/34] lsm: cleanup the debug and console output " Paul Moore
2025-07-24 23:32 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 21/34] lsm: output available LSMs when debugging Paul Moore
2025-07-24 23:33 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 22/34] lsm: group lsm_order_parse() with the other lsm_order_*() functions Paul Moore
2025-07-24 23:34 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 23/34] lsm: introduce an initcall mechanism into the LSM framework Paul Moore
2025-07-24 23:35 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 24/34] loadpin: move initcalls to " Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 25/34] ipe: " Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 26/34] smack: " Paul Moore
2025-07-24 23:36 ` Casey Schaufler
2025-07-28 9:46 ` Roberto Sassu [this message]
2025-07-28 22:34 ` Paul Moore
2025-07-28 23:56 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 27/34] tomoyo: " Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 28/34] safesetid: " Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 29/34] apparmor: " Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 30/34] lockdown: " Paul Moore
2025-07-25 8:12 ` Xiu Jianfeng
2025-07-25 16:51 ` Paul Moore
2025-07-26 9:38 ` xiujianfeng
2025-07-28 21:49 ` Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 31/34] ima,evm: " Paul Moore
2025-07-21 23:30 ` Paul Moore
2025-07-21 23:34 ` Paul Moore
2025-07-28 9:46 ` Nicolas Bouchinet
2025-07-28 10:43 ` Roberto Sassu
2025-07-28 23:17 ` Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 32/34] selinux: " Paul Moore
2025-07-21 23:21 ` [RFC PATCH v2 33/34] lsm: consolidate all of the LSM framework initcalls Paul Moore
2025-07-24 23:37 ` Casey Schaufler
2025-07-21 23:21 ` [RFC PATCH v2 34/34] lsm: add a LSM_STARTED_ALL notification event Paul Moore
2025-07-24 23:38 ` Casey Schaufler
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=5ff016adea8969e4a97387d4ed88a172bdc4b3de.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.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=paul@paul-moore.com \
--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).