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-20250926
Date: Fri, 26 Sep 2025 23:07:34 -0400 [thread overview]
Message-ID: <6edbd0e6dc79902981bf9a34e8d41128@paul-moore.com> (raw)
Linus,
Here are the SELinux patches for the upcoming Linux v6.18 merge window:
- Support per-file labeling for functionfs
Both genfscon and user defined labeling methods are supported. This
should help users who want to provide separation between the control
endpoint file, "ep0", and other endpoints.
- Remove our use of get_zeroed_page() in sel_read_bool()
Update sel_read_bool() to use a four byte stack buffer instead of a
memory page fetched via get_zeroed_page(), and fix a memory in the
process.
Needless to say we should have done this a long time ago, but it was
in a very old chunk of code that "just worked" and I don't think
anyone had taken a real look at it in many years.
- Better use of the netdev skb/sock helper functions
Convert a sk_to_full_sk(skb->sk) into a skb_to_full_sk(skb) call.
- Remove some old, dead, and/or redundant code
Paul
--
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20250926
for you to fetch changes up to 68e1e908cb7682db9fb7f79907f9352435a81c0f:
selinux: enable per-file labeling for functionfs
(2025-09-07 12:54:56 -0400)
----------------------------------------------------------------
selinux/stable-6.18 PR 20250926
----------------------------------------------------------------
Neill Kapron (1):
selinux: enable per-file labeling for functionfs
Qianfeng Rong (1):
selinux: Remove redundant __GFP_NOWARN
Stephen Smalley (1):
selinux: fix sel_read_bool() allocation and error handling
Tianjia Zhang (1):
selinux: use a consistent method to get full socket from skb
Yue Haibing (1):
selinux: Remove unused function selinux_policycap_netif_wildcard()
security/selinux/avc.c | 13 ++++++-------
security/selinux/hooks.c | 10 +++++++---
security/selinux/include/policycap.h | 1 +
security/selinux/include/policycap_names.h | 1 +
security/selinux/include/security.h | 4 ++--
security/selinux/selinuxfs.c | 18 +++++-------------
6 files changed, 22 insertions(+), 25 deletions(-)
--
paul-moore.com
next reply other threads:[~2025-09-27 3:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 3:07 Paul Moore [this message]
2025-09-30 15:48 ` [GIT PULL] selinux/selinux-pr-20250926 Linus Torvalds
2025-09-30 16:06 ` Paul Moore
2025-09-30 17:35 ` 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=6edbd0e6dc79902981bf9a34e8d41128@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;
as well as URLs for NNTP newsgroup(s).