From: Steven Moreland <smoreland@google.com>
To: paul@paul-moore.com, sds@tycho.nsa.gov, eparis@parisplace.org,
keescook@chromium.org, anton@enomsg.org, ccross@android.com,
tony.luck@intel.com, selinux@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Cc: "Connor O'Brien" <connoro@google.com>,
Steven Moreland <smoreland@google.com>
Subject: [PATCH] security: selinux: allow per-file labeling for bpffs
Date: Thu, 6 Feb 2020 08:55:27 -0800 [thread overview]
Message-ID: <20200206165527.211350-1-smoreland@google.com> (raw)
From: Connor O'Brien <connoro@google.com>
Add support for genfscon per-file labeling of bpffs files. This allows
for separate permissions for different pinned bpf objects, which may
be completely unrelated to each other.
Change-Id: I03ae28d3afea70acd6dc53ebf810b34b357b6eb5
Signed-off-by: Connor O'Brien <connoro@google.com>
Signed-off-by: Steven Moreland <smoreland@google.com>
---
security/selinux/hooks.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
index de4887742d7c..4f9396e6ce8c 100644
--- a/security/selinux/hooks.c
+++ b/security/selinux/hooks.c
@@ -872,6 +872,7 @@ static int selinux_set_mnt_opts(struct super_block *sb,
!strcmp(sb->s_type->name, "sysfs") ||
!strcmp(sb->s_type->name, "pstore") ||
!strcmp(sb->s_type->name, "binder") ||
+ !strcmp(sb->s_type->name, "bpf") ||
!strcmp(sb->s_type->name, "cgroup") ||
!strcmp(sb->s_type->name, "cgroup2"))
sbsec->flags |= SE_SBGENFS;
--
2.25.0.341.g760bfbb309-goog
next reply other threads:[~2020-02-06 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 16:55 Steven Moreland [this message]
2020-02-06 17:21 ` Stephen Smalley
2020-02-06 17:35 ` Stephen Smalley
2020-02-06 17:41 ` Steven Moreland
2020-02-06 18:12 ` Stephen Smalley
2020-02-12 3:17 ` Paul Moore
2020-02-12 17:46 ` Steven Moreland
2020-02-12 18:09 ` 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=20200206165527.211350-1-smoreland@google.com \
--to=smoreland@google.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=connoro@google.com \
--cc=eparis@parisplace.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=tony.luck@intel.com \
/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®