From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] lsm/lsm-pr-20260615
Date: Mon, 15 Jun 2026 22:55:38 -0400 [thread overview]
Message-ID: <9b359189953cc739f62fc94af4c24a27@paul-moore.com> (raw)
Linus,
A single LSM framework patch to update the security_inode_listsecurity()
hook to be able to leverage the xattr_list_one() helper function. We
wanted to do this for a while, but we needed to fixup the callers in the
NFS code first. With the NFS code changes shipping in Linux v7.0 and
no one complaining, it seemed a good time to complete the shift.
Paul
--
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
tags/lsm-pr-20260615
for you to fetch changes up to f71ece9712b7712df98871eea9aeb60e49ca5239:
security,fs,nfs,net: update security_inode_listsecurity() interface
(2026-05-01 11:29:33 -0400)
----------------------------------------------------------------
lsm/stable-7.2 PR 20260615
----------------------------------------------------------------
Stephen Smalley (1):
security,fs,nfs,net: update security_inode_listsecurity()
interface
fs/nfs/nfs4proc.c | 7 ++-----
fs/xattr.c | 11 +++++++----
include/linux/lsm_hook_defs.h | 4 ++--
include/linux/security.h | 5 +++--
security/security.c | 16 ++++++++--------
security/selinux/hooks.c | 10 +++-------
security/smack/smack_lsm.c | 13 ++++---------
7 files changed, 29 insertions(+), 37 deletions(-)
--
paul-moore.com
next reply other threads:[~2026-06-16 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 2:55 Paul Moore [this message]
2026-06-17 11:59 ` [GIT PULL] lsm/lsm-pr-20260615 pr-tracker-bot
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=9b359189953cc739f62fc94af4c24a27@paul-moore.com \
--to=paul@paul-moore.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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