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
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 1/3] LSM: Add mount opts blob size tracking
Date: Wed, 06 Aug 2025 18:06:11 -0400 [thread overview]
Message-ID: <3e45e20228c80f9f6a126d09208ff995@paul-moore.com> (raw)
In-Reply-To: <20250617210105.17479-2-casey@schaufler-ca.com>
On Jun 17, 2025 Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> Add mount option data to the blob size accounting in anticipation
> of using a shared mnt_opts blob.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> ---
> include/linux/lsm_hooks.h | 1 +
> security/lsm_init.c | 2 ++
> security/selinux/hooks.c | 1 +
> security/smack/smack_lsm.c | 1 +
> 4 files changed, 5 insertions(+)
Since you're respinning this patchset for other reasons, just base it
on the existing LSM initialization code. If this patchset collides with
the init rework mid-flight I'll handle the merge fixup.
I appreciate the consideration, but in this case I think it's easier to
not have the dependency.
--
paul-moore.com
next prev parent reply other threads:[~2025-08-06 22:06 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 ` [PATCH 0/3] LSM: Multiple LSM mount options Casey Schaufler
2025-06-17 21:01 ` [PATCH 1/3] LSM: Add mount opts blob size tracking Casey Schaufler
2025-08-06 22:06 ` Paul Moore [this message]
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=3e45e20228c80f9f6a126d09208ff995@paul-moore.com \
--to=paul@paul-moore.com \
--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