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-20260903
Date: Thu, 03 Sep 2026 16:35:27 -0400 [thread overview]
Message-ID: <8c72adc9e5a9d3ce854fab61ec5f66df@paul-moore.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
Linus,
Two SELinux fixes for the next Linux v7.3-rcX release: one to fix how we
lookup a BPF token's creator label to prevent a possible TOCTOU, and one
to update Ondrej's email address.
Paul
--
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20260903
for you to fetch changes up to 4299767d772d4e498998e32157e45841178ab192:
MAINTAINERS, mailmap: update email address for Ondrej Mosnáček
(2026-09-03 16:24:05 -0400)
----------------------------------------------------------------
selinux/stable-7.3 PR 20260903
----------------------------------------------------------------
Ondrej Mosnáček (1):
MAINTAINERS, mailmap: update email address for Ondrej Mosnáček
Paul Moore (1):
selinux: fix BPF token permission checks
.mailmap | 1 +
MAINTAINERS | 2 +-
security/selinux/hooks.c | 36 ++++++++++--------------------------
3 files changed, 12 insertions(+), 27 deletions(-)
--
paul-moore.com
next reply other threads:[~2026-09-03 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 20:35 Paul Moore [this message]
2026-09-03 20:46 ` [GIT PULL] selinux/selinux-pr-20260903 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=8c72adc9e5a9d3ce854fab61ec5f66df@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