From: Paul Moore <paul@paul-moore.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
casey@schaufler-ca.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, mic@digikod.net,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3 3/5] LSM: Use lsm_context in security_inode_getsecctx
Date: Thu, 31 Oct 2024 18:53:39 -0400 [thread overview]
Message-ID: <5e5c5e04ff82a8a8e94f02ecbe63b1fd@paul-moore.com> (raw)
In-Reply-To: <20241023212158.18718-4-casey@schaufler-ca.com>
On Oct 23, 2024 Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> Change the security_inode_getsecctx() interface to fill a lsm_context
> structure instead of data and length pointers. This provides
> the information about which LSM created the context so that
> security_release_secctx() can use the correct hook.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> Cc: linux-nfs@vger.kernel.org
> ---
> fs/nfsd/nfs4xdr.c | 26 ++++++++++----------------
> include/linux/lsm_hook_defs.h | 4 ++--
> include/linux/security.h | 5 +++--
> security/security.c | 12 ++++++------
> security/selinux/hooks.c | 10 ++++++----
> security/smack/smack_lsm.c | 7 ++++---
> 6 files changed, 31 insertions(+), 33 deletions(-)
See my note on patch 1/5, merging into lsm/dev.
--
paul-moore.com
next prev parent reply other threads:[~2024-10-31 22:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241023212158.18718-1-casey@schaufler-ca.com>
2024-10-23 21:21 ` [PATCH v3 1/5] LSM: Ensure the correct LSM context releaser Casey Schaufler
2024-10-31 22:53 ` Paul Moore
2024-12-06 20:05 ` Kees Bakker
2024-12-06 20:57 ` Casey Schaufler
2024-10-23 21:21 ` [PATCH v3 3/5] LSM: Use lsm_context in security_inode_getsecctx Casey Schaufler
2024-10-31 22:53 ` Paul Moore [this message]
2024-10-23 21:21 ` [PATCH v3 4/5] LSM: lsm_context in security_dentry_init_security Casey Schaufler
2024-10-31 22:53 ` Paul Moore
2025-02-20 16:43 ` Stephen Smalley
2025-02-20 17:40 ` Paul Moore
2025-02-20 17:52 ` Casey Schaufler
2025-02-20 17:53 ` Paul Moore
2025-02-20 18:02 ` Stephen Smalley
2025-02-20 18:15 ` Casey Schaufler
2025-02-20 18:16 ` Stephen Smalley
2025-02-20 19:33 ` Casey Schaufler
2025-02-20 19:37 ` Stephen Smalley
2025-02-20 20:31 ` Casey Schaufler
2025-02-20 20:33 ` Stephen Smalley
2025-02-20 21:08 ` Casey Schaufler
2025-02-21 3:16 ` Paul Moore
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=5e5c5e04ff82a8a8e94f02ecbe63b1fd@paul-moore.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--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