From: Eric Suen <ericsu@linux.microsoft.com>
To: selinux@vger.kernel.org
Subject: [PATCH userspace v2] libsepol: add bpf_token_perms polcap
Date: Wed, 8 Oct 2025 16:33:04 -0700 [thread overview]
Message-ID: <20251008233305.2098-1-ericsu@linux.microsoft.com> (raw)
New policy capability 'bpf_token_perms' required by patch to support SELinux
for BPF token control:
https://lore.kernel.org/selinux/20250806180149.1995-1-ericsu@linux.microsoft.com/
Signed-off-by: Eric Suen <ericsu@linux.microsoft.com>
---
Changes in v2:
- Rebase to the latest changes
libsepol/include/sepol/policydb/polcaps.h | 1 +
libsepol/src/polcaps.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/libsepol/include/sepol/policydb/polcaps.h b/libsepol/include/sepol/policydb/polcaps.h
index 5a3fbdb4..ef529e76 100644
--- a/libsepol/include/sepol/policydb/polcaps.h
+++ b/libsepol/include/sepol/policydb/polcaps.h
@@ -21,6 +21,7 @@ enum {
POLICYDB_CAP_GENFS_SECLABEL_WILDCARD,
POLICYDB_CAP_FUNCTIONFS_SECLABEL,
POLICYDB_CAP_MEMFD_CLASS,
+ POLICYDB_CAP_BPF_TOKEN_PERMS,
__POLICYDB_CAP_MAX
};
#define POLICYDB_CAP_MAX (__POLICYDB_CAP_MAX - 1)
diff --git a/libsepol/src/polcaps.c b/libsepol/src/polcaps.c
index 526f35ed..31b52d70 100644
--- a/libsepol/src/polcaps.c
+++ b/libsepol/src/polcaps.c
@@ -20,6 +20,7 @@ static const char * const polcap_names[POLICYDB_CAP_MAX + 1] = {
[POLICYDB_CAP_GENFS_SECLABEL_WILDCARD] = "genfs_seclabel_wildcard",
[POLICYDB_CAP_FUNCTIONFS_SECLABEL] = "functionfs_seclabel",
[POLICYDB_CAP_MEMFD_CLASS] = "memfd_class",
+ [POLICYDB_CAP_BPF_TOKEN_PERMS] = "bpf_token_perms",
};
int sepol_polcap_getnum(const char *name)
--
2.50.1
next reply other threads:[~2025-10-08 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 23:33 Eric Suen [this message]
2025-10-09 15:39 ` [PATCH userspace v2] libsepol: add bpf_token_perms polcap Stephen Smalley
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=20251008233305.2098-1-ericsu@linux.microsoft.com \
--to=ericsu@linux.microsoft.com \
--cc=selinux@vger.kernel.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).