From: Stephen Smalley <sds@tycho.nsa.gov>
To: Steven Moreland <smoreland@google.com>,
paul@paul-moore.com, 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>
Subject: Re: [PATCH v2] security: selinux: allow per-file labeling for bpffs
Date: Fri, 7 Feb 2020 10:49:32 -0500 [thread overview]
Message-ID: <a4344c6a-3916-a119-1f5c-5c2129b415f9@tycho.nsa.gov> (raw)
In-Reply-To: <20200206211430.150615-1-smoreland@google.com>
On 2/6/20 4:14 PM, Steven Moreland wrote:
> 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.
>
> Signed-off-by: Connor O'Brien <connoro@google.com>
> Signed-off-by: Steven Moreland <smoreland@google.com>
Is this relative to the next branch of the selinux git tree?
Doesn't apply for me.
> ---
> security/selinux/hooks.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
> index 116b4d644f68..d7b11188dc8d 100644
> --- a/security/selinux/hooks.c
> +++ b/security/selinux/hooks.c
> @@ -750,7 +750,8 @@ static int selinux_set_mnt_opts(struct super_block *sb,
> if (strcmp(sb->s_type->name, "proc") == 0)
> sbsec->flags |= SE_SBPROC | SE_SBGENFS;
>
> - if (!strcmp(sb->s_type->name, "debugfs") ||
> + if (!strcmp(sb->s_type->name, "bpf") ||
> + !strcmp(sb->s_type->name, "debugfs") ||
> !strcmp(sb->s_type->name, "tracefs") ||
> !strcmp(sb->s_type->name, "pstore"))
> sbsec->flags |= SE_SBGENFS;
>
prev parent reply other threads:[~2020-02-07 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 21:14 [PATCH v2] security: selinux: allow per-file labeling for bpffs Steven Moreland
2020-02-07 15:49 ` Stephen Smalley [this message]
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=a4344c6a-3916-a119-1f5c-5c2129b415f9@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--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=selinux@vger.kernel.org \
--cc=smoreland@google.com \
--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;
as well as URLs for NNTP newsgroup(s).