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-20250107
Date: Tue, 07 Jan 2025 16:08:48 -0500 [thread overview]
Message-ID: <c3eecfb79581eed47b37aac6b1ab8432@paul-moore.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
Linus,
A single SELinux patch to address a problem with a single domain using
multiple xperm classes, please merge.
-Paul
--
The following changes since commit 900f83cf376bdaf798b6f5dcb2eae0c822e908b6:
selinux: ignore unknown extended permissions (2024-12-15 21:59:03 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20250107
for you to fetch changes up to 5e7f0efd23238039bcd4fc72ff28d94f364ec26b:
selinux: match extended permissions to their base permissions
(2025-01-04 20:58:46 -0500)
----------------------------------------------------------------
selinux/stable-6.13 PR 20250107
----------------------------------------------------------------
Thiébaud Weksteen (1):
selinux: match extended permissions to their base permissions
security/selinux/avc.c | 61 +++++++++++++++-------------
security/selinux/hooks.c | 6 +-
security/selinux/include/avc.h | 5 +-
security/selinux/include/security.h | 3 +
security/selinux/ss/services.c | 28 +++++++++---
5 files changed, 65 insertions(+), 38 deletions(-)
--
paul-moore.com
next reply other threads:[~2025-01-07 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 21:08 Paul Moore [this message]
2025-01-07 23:47 ` [GIT PULL] selinux/selinux-pr-20250107 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=c3eecfb79581eed47b37aac6b1ab8432@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