mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Antonio Murdaca <amurdaca@redhat.com>
To: selinux@tycho.nsa.gov
Cc: gary.tierney@gmx.com, linux-kernel@vger.kernel.org,
	dwalsh@redhat.com, pmoore@redhat.com, vgoyal@redhat.com,
	cgroups@vger.kernel.org
Subject: [PATCH] security: selinux: allow per-file labeling for cgroupfs
Date: Thu,  9 Feb 2017 16:58:23 +0100	[thread overview]
Message-ID: <20170209155823.22148-1-runcom@redhat.com> (raw)

This patch allows genfscon per-file labeling for cgroupfs. For instance,
this allows to label the "release_agent" file within each
cgroup mount and limit writes to it.

Signed-off-by: Antonio Murdaca <runcom@redhat.com>
---
 security/selinux/hooks.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
index 9a8f12f..5a3138e 100644
--- a/security/selinux/hooks.c
+++ b/security/selinux/hooks.c
@@ -808,6 +808,8 @@ static int selinux_set_mnt_opts(struct super_block *sb,
 
 	if (!strcmp(sb->s_type->name, "debugfs") ||
 	    !strcmp(sb->s_type->name, "sysfs") ||
+	    !strcmp(sb->s_type->name, "cgroup") ||
+	    !strcmp(sb->s_type->name, "cgroup2") ||
 	    !strcmp(sb->s_type->name, "pstore"))
 		sbsec->flags |= SE_SBGENFS;
 
-- 
2.9.3

             reply	other threads:[~2017-02-09 16:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 15:58 Antonio Murdaca [this message]
2017-03-10 20:01 ` Paul Moore
2017-03-10 20:17   ` Stephen Smalley
2017-03-10 20:21     ` Paul Moore
2017-08-22 19:47       ` Paul Moore
2017-02-09 16:02 Antonio Murdaca
2017-02-09 16:14 ` Paul Moore
     [not found]   ` <CALKLTGTc7U7ohxd44MHOuzVomW-oUsumqUqr0MKaUohw1NpSsg@mail.gmail.com>
2017-02-09 19:23     ` Paul Moore
     [not found]       ` <CALKLTGTjpBYd5-M9RiO-Q4H_SokEiPJYptbxktg_aPccws59Jw@mail.gmail.com>
2017-02-09 23:04         ` Paul Moore
2017-02-10 23:05           ` Daniel J Walsh

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=20170209155823.22148-1-runcom@redhat.com \
    --to=amurdaca@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=dwalsh@redhat.com \
    --cc=gary.tierney@gmx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmoore@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=vgoyal@redhat.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

Powered by JetHome