From: Paul Moore <paul@paul-moore.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
casey@schaufler-ca.com, eparis@redhat.com,
linux-security-module@vger.kernel.org, audit@vger.kernel.org
Cc: jmorris@namei.org, serge@hallyn.com, keescook@chromium.org,
john.johansen@canonical.com, penguin-kernel@i-love.sakura.ne.jp,
stephen.smalley.work@gmail.com, linux-kernel@vger.kernel.org,
selinux@vger.kernel.org
Subject: Re: [PATCH v4 2/4] LSM: security_lsmblob_to_secctx module selection
Date: Mon, 16 Jun 2025 16:54:50 -0400 [thread overview]
Message-ID: <b6295394c101221e5a4aacd0abf021ce@paul-moore.com> (raw)
In-Reply-To: <20250607005134.10488-3-casey@schaufler-ca.com>
On Jun 6, 2025 Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> Add a parameter lsmid to security_lsmblob_to_secctx() to identify which
> of the security modules that may be active should provide the security
> context. If the value of lsmid is LSM_ID_UNDEF the first LSM providing
> a hook is used. security_secid_to_secctx() is unchanged, and will
> always report the first LSM providing a hook.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> ---
> include/linux/security.h | 6 ++++--
> kernel/audit.c | 4 ++--
> kernel/auditsc.c | 8 +++++---
> net/netlabel/netlabel_user.c | 3 ++-
> security/security.c | 13 +++++++++++--
> 5 files changed, 24 insertions(+), 10 deletions(-)
...
> diff --git a/security/security.c b/security/security.c
> index 2b9dde02f4de..306860434200 100644
> --- a/security/security.c
> +++ b/security/security.c
> @@ -3774,6 +3774,7 @@ EXPORT_SYMBOL(security_ismaclabel);
> * security_secid_to_secctx() - Convert a secid to a secctx
> * @secid: secid
> * @cp: the LSM context
> + * @lsmid: which security module to report
> *
> * Convert secid to security context. If @cp is NULL the length of the
> * result will be returned, but no data will be returned. This
You're updating the comment block for the wrong function.
> @@ -3800,9 +3801,17 @@ EXPORT_SYMBOL(security_secid_to_secctx);
> *
> * Return: Return length of data on success, error on failure.
> */
Since you need to update the patch to fix the problem above, it would
probably be a good thing to explain the LSM_ID_UNDEF handling in the
function's comment block as you did in the commit description.
> -int security_lsmprop_to_secctx(struct lsm_prop *prop, struct lsm_context *cp)
> +int security_lsmprop_to_secctx(struct lsm_prop *prop, struct lsm_context *cp,
> + int lsmid)
> {
> - return call_int_hook(lsmprop_to_secctx, prop, cp);
> + struct lsm_static_call *scall;
> +
> + lsm_for_each_hook(scall, lsmprop_to_secctx) {
> + if (lsmid != LSM_ID_UNDEF && lsmid != scall->hl->lsmid->id)
> + continue;
> + return scall->hl->hook.lsmprop_to_secctx(prop, cp);
> + }
> + return LSM_RET_DEFAULT(lsmprop_to_secctx);
> }
> EXPORT_SYMBOL(security_lsmprop_to_secctx);
>
> --
> 2.47.0
--
paul-moore.com
next prev parent reply other threads:[~2025-06-16 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250607005134.10488-1-casey.ref@schaufler-ca.com>
2025-06-07 0:51 ` [PATCH v4 0/4] Audit: Records for multiple security contexts Casey Schaufler
2025-06-07 0:51 ` [PATCH v4 1/4] Audit: Create audit_stamp structure Casey Schaufler
2025-06-07 0:51 ` [PATCH v4 2/4] LSM: security_lsmblob_to_secctx module selection Casey Schaufler
2025-06-16 20:54 ` Paul Moore [this message]
2025-06-07 0:51 ` [PATCH v4 3/4] Audit: Add record for multiple task security contexts Casey Schaufler
2025-06-16 20:54 ` Paul Moore
2025-06-07 0:51 ` [PATCH v4 4/4] Audit: Add record for multiple object contexts Casey Schaufler
2025-06-16 20:54 ` Paul Moore
2025-07-04 20:18 ` Casey Schaufler
2025-07-15 20:40 ` 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=b6295394c101221e5a4aacd0abf021ce@paul-moore.com \
--to=paul@paul-moore.com \
--cc=audit@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.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