From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Cc: stephen.smalley.work@gmail.com
Subject: Re: [PATCH ported/repost v2] security,fs,nfs,net: update security_inode_listsecurity() interface
Date: Fri, 1 May 2026 12:00:55 -0400 [thread overview]
Message-ID: <CAHC9VhSyDVLOQ2vr0YL1PUCdS-jh0gvwcDruW1f6t9g1WTDS7Q@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhSDPg2U9UYZ7Na_A8RA-KN8OsNj5S+QwscW6X20tojhjA@mail.gmail.com>
On Tue, Apr 28, 2026 at 3:26 PM Paul Moore <paul@paul-moore.com> wrote:
> On Tue, Apr 28, 2026 at 3:21 PM Paul Moore <paul@paul-moore.com> wrote:
> >
> > From: Stephen Smalley <stephen.smalley.work@gmail.com>
> >
> > Update the security_inode_listsecurity() interface to allow
> > use of the xattr_list_one() helper and update the hook
> > implementations.
> >
> > Link: https://lore.kernel.org/selinux/20250424152822.2719-1-stephen.smalley.work@gmail.com
> > Signed-off-by: Stephen Smalley <stephen.smalley.work@gmail.com>
> > [PM: forward porting to bring this patch up to v7.1-rc1+]
> > Signed-off-by: Paul Moore <paul@paul-moore.com>
> > ---
> > 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(-)
>
> With the security_inode_listsecurity() cleanup shipping in Linux v7.0,
> I wanted to get this patch ready for the next merge window. As
> expected, some borderline non-trivial porting was needed, so I'm
> posting the ported version in case anyone wants to review the patch
> again. If I don't hear anything over the next few days, I'll plan to
> merge this into lsm/dev later this week.
This has now been merged into lsm/dev, thanks all.
> The SELinux test suite runs clean for both local and NFS test runs.
--
paul-moore.com
prev parent reply other threads:[~2026-05-01 16:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 19:50 [PATCH v2] security,fs,nfs,net: update security_inode_listsecurity() interface Stephen Smalley
2025-04-29 7:46 ` Christian Brauner
2025-04-29 12:25 ` Stephen Smalley
2025-04-29 23:34 ` Paul Moore
2025-05-20 21:31 ` Paul Moore
2025-05-21 0:22 ` Casey Schaufler
2025-05-27 21:03 ` Anna Schumaker
2025-06-19 21:18 ` Paul Moore
2025-07-24 2:09 ` Paul Moore
2025-12-03 15:35 ` Stephen Smalley
2025-12-03 15:55 ` Paul Moore
2025-12-03 18:08 ` Stephen Smalley
2025-12-03 20:01 ` Stephen Smalley
2025-06-05 18:09 ` Stephen Smalley
2025-06-05 18:24 ` Paul Moore
2025-05-21 0:31 ` Kuniyuki Iwashima
2025-06-19 21:04 ` Paul Moore
2025-06-06 13:39 ` Konstantin Andreev
2025-06-06 14:28 ` Stephen Smalley
2025-06-06 15:24 ` Konstantin Andreev
2026-04-28 19:21 ` [PATCH ported/repost " Paul Moore
2026-04-28 19:26 ` Paul Moore
2026-05-01 16:00 ` Paul Moore [this message]
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=CAHC9VhSyDVLOQ2vr0YL1PUCdS-jh0gvwcDruW1f6t9g1WTDS7Q@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).