From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] SELinux support for cgroup2 filesystem.
Date: Thu, 31 Mar 2016 08:32:59 -0400 [thread overview]
Message-ID: <56FD18FB.8010303@tresys.com> (raw)
In-Reply-To: <1459419990-2755-1-git-send-email-lvrabec@redhat.com>
On 3/31/2016 6:26 AM, Lukas Vrabec wrote:
> With the new "cgroup2" system added in kernel 4.5, systemd is getting
> selinux denials when manipulating the cgroup hierarchy.
>
> Pull request in systemd with cgroup2 support:
> https://github.com/systemd/systemd/pull/2903
>
> AVC when writing process numbers to move them to the right cgroup:
> Mar 29 19:58:30 rawhide kernel: audit: type=1400
> audit(1459295910.257:68): avc: denied { write } for pid=1
> comm="systemd" name="cgroup.procs" dev="cgroup2" ino=6
> scontext=system_u:system_r:init_t:s0
> tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1
>
> In this case new filesystem "cgroup2" need to be labeled as cgroup_t.
Merged.
> Signed-off-by: Lukas Vrabec <lvrabec@redhat.com>
> ---
> policy/modules/kernel/filesystem.te | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/policy/modules/kernel/filesystem.te b/policy/modules/kernel/filesystem.te
> index 14afaa8..1b28e23 100644
> --- a/policy/modules/kernel/filesystem.te
> +++ b/policy/modules/kernel/filesystem.te
> @@ -77,6 +77,7 @@ fs_type(cgroup_t)
> files_mountpoint(cgroup_t)
> dev_associate_sysfs(cgroup_t)
> genfscon cgroup / gen_context(system_u:object_r:cgroup_t,s0)
> +genfscon cgroup2 / gen_context(system_u:object_r:cgroup_t,s0)
>
> type configfs_t;
> fs_type(configfs_t)
>
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2016-03-31 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 10:26 [refpolicy] [PATCH 1/1] SELinux support for cgroup2 filesystem Lukas Vrabec
2016-03-31 12:32 ` Christopher J. PeBenito [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=56FD18FB.8010303@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.