From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] selinux/selinux-pr-20260501
Date: Fri, 01 May 2026 16:05:34 -0400 [thread overview]
Message-ID: <c40ca3bb83a27f66229acd4fe3888e78@paul-moore.com> (raw)
Linus,
Three SELinux patches to address issues found in Linux v7.1-rcX (and
earlier):
- Ensure SELinux is always properly accessing it's own sock LSM state
- Only reserve an xattr slot for SELinux if it will be used
- Fix a SELinux auditing regression in the directory avdcache
Just as a FYI, I expect there will be some additional v7.1-rcX patches
next week, but they aren't ready quite yet.
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/selinux.git
tags/selinux-pr-20260501
for you to fetch changes up to f92d542577db878acfd21cc18dab23d03023b217:
selinux: fix avdcache auditing (2026-04-28 18:13:58 -0400)
----------------------------------------------------------------
selinux/stable-7.1 PR 20260501
----------------------------------------------------------------
David Windsor (1):
selinux: don't reserve xattr slot when we won't fill it
Stephen Smalley (1):
selinux: fix avdcache auditing
Zongyao Chen (1):
selinux: use sk blob accessor in socket permission helpers
security/selinux/hooks.c | 38 +++++++++++++-----------------
security/selinux/include/objsec.h | 4 ---
2 files changed, 18 insertions(+), 24 deletions(-)
--
paul-moore.com
next reply other threads:[~2026-05-01 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 20:05 Paul Moore [this message]
2026-05-01 20:22 ` [GIT PULL] selinux/selinux-pr-20260501 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=c40ca3bb83a27f66229acd4fe3888e78@paul-moore.com \
--to=paul@paul-moore.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@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