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-20261005
Date: Mon, 05 Oct 2026 06:24:05 -0400 [thread overview]
Message-ID: <32b99c092d7a668f114cecb3ecb22c28@paul-moore.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
Linus,
Two SELinux patches for the next Linux v7.3-rcX release:
- Preserve SECURITY_LSM_NATIVE_LABELS when reusing superblocks
Similar to a previous fix (see the commit description of Stephen's fix)
we need to check to see if we have already mounted/setup the superblock
passed into the security_sb_set_mnt_opts() LSM hook so we don't mistakenly
unset SECURITY_LSM_NATIVE_LABELS.
- Fix a potential AVC sequence number data race
Thanks,
Paul
--
The following changes since commit 93f51579e7df248780214094418f205253383cc5:
Linux 7.3-rc4 (2026-09-20 13:48:15 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20261005
for you to fetch changes up to 28b7260548af3d35773477993ad4e4de41578dd7:
selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts
(2026-09-30 15:10:41 -0400)
----------------------------------------------------------------
selinux/stable-7.3 PR 20261005
----------------------------------------------------------------
Christian Göttsche (1):
selinux: fix data race on AVC latest_notif
Stephen Smalley (1):
selinux: preserve NATIVE_LABELS on already-initialized sb in
set_mnt_opts
security/selinux/avc.c | 5 +++--
security/selinux/hooks.c | 9 ++++++++-
2 files changed, 11 insertions(+), 3 deletions(-)
--
paul-moore.com
next reply other threads:[~2026-10-05 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 10:24 Paul Moore [this message]
2026-10-05 14:41 ` 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=32b99c092d7a668f114cecb3ecb22c28@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
all inboxes | Powered by JetHome®