From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [ patch 1/1] Cgroup: needs to mount to /sys/fs/cgroup.
Date: Mon, 11 Oct 2010 17:34:34 +0200 [thread overview]
Message-ID: <20101011153428.GA14369@localhost.localdomain> (raw)
In-Reply-To: <4CB320B3.4090101@tresys.com>
On Mon, Oct 11, 2010 at 10:35:31AM -0400, Christopher J. PeBenito wrote:
> On 10/09/10 09:39, Paul Howarth wrote:
> > On Fri, 8 Oct 2010 23:28:01 +0200
> > Dominick Grift<domg472@gmail.com> wrote:
> >
> >> I am not sure why libcgroup is moving locations for cgroupfs. Seems
> >> they now use /cgroup again, where they were using /sys/fs/cgroup a
> >> version before.
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=640282
> >
> > It'll move back again for F-15.
>
> I'm going to pass on this change for now.
Good call, it wont work anyways. sysfs is a pseudo fs so type cgroup_t for /sys/fs/cgroup wont apply at boot.
So if they move to that location we either need to allow libcgroup to mounon sysfs_t or it needs some magic in the kernel to label that dir cgroup_t.
But thats for f15..
i do have some cgroup related patches in the pipeline for f14 (initrc_t (cgreds and cgconfigs rc scripts need to read their config files :( )
>
> --
> Chris PeBenito
> Tresys Technology, LLC
> www.tresys.com | oss.tresys.com
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20101011/9c25361f/attachment.bin
prev parent reply other threads:[~2010-10-11 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 21:28 [refpolicy] [ patch 1/1] Cgroup: needs to mount to /sys/fs/cgroup Dominick Grift
2010-10-09 13:39 ` Paul Howarth
2010-10-11 14:35 ` Christopher J. PeBenito
2010-10-11 15:34 ` Dominick Grift [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=20101011153428.GA14369@localhost.localdomain \
--to=domg472@gmail.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.