From: Casey Schaufler <casey@schaufler-ca.com>
To: casey@schaufler-ca.com, paul@paul-moore.com, eparis@redhat.com,
linux-security-module@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: [PATCH 0/3] LSM: Multiple LSM mount options
Date: Tue, 17 Jun 2025 14:01:02 -0700 [thread overview]
Message-ID: <20250617210105.17479-1-casey@schaufler-ca.com> (raw)
In-Reply-To: 20250617210105.17479-1-casey.ref@schaufler-ca.com
Linux Security Module (LSM) that support mount options, currently SELinux
and Smack, allocate their own data for those options. This patch set
moves the handling of mount option data out of the individual LSMs and
into the LSM infrastructure. This allows for multiple LSMs to support
mount options at the same time.
https://github.com/cschaufler/lsm-stacking#mount-opts-6.16-rc1
Based on patches Paul Moore's LSM initialization patchset.
https://lore.kernel.org/all/20250409185019.238841-31-paul@paul-moore.com/v3
Casey Schaufler (3):
LSM: Add mount opts blob size tracking
LSM: allocate mnt_opts blobs instead of module specific data
LSM: Infrastructure management of the mnt_opts security blob
include/linux/lsm_hooks.h | 2 ++
security/lsm_init.c | 2 ++
security/security.c | 26 ++++++++++-----
security/selinux/hooks.c | 65 +++++++++++++++++++++++++-------------
security/smack/smack_lsm.c | 62 +++++++++++++++++++++++++-----------
5 files changed, 108 insertions(+), 49 deletions(-)
--
2.47.0
next parent reply other threads:[~2025-06-17 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250617210105.17479-1-casey.ref@schaufler-ca.com>
2025-06-17 21:01 ` Casey Schaufler [this message]
2025-06-17 21:01 ` [PATCH 1/3] LSM: Add mount opts blob size tracking Casey Schaufler
2025-08-06 22:06 ` Paul Moore
2025-06-17 21:01 ` [PATCH 2/3] LSM: allocate mnt_opts blobs instead of module specific data Casey Schaufler
2025-08-06 22:06 ` Paul Moore
2025-08-06 23:16 ` Casey Schaufler
2025-08-07 0:40 ` Paul Moore
2025-06-17 21:01 ` [PATCH 3/3] LSM: Infrastructure management of the mnt_opts security blob 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=20250617210105.17479-1-casey@schaufler-ca.com \
--to=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=paul@paul-moore.com \
--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