All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] kernel_filesystem.patch
Date: Mon, 07 Jun 2010 12:50:24 -0400	[thread overview]
Message-ID: <4C0D2350.5090004@redhat.com> (raw)
In-Reply-To: <1275925288.809.119.camel@gorn.columbia.tresys.com>

On 06/07/2010 11:41 AM, Christopher J. PeBenito wrote:
> On Mon, 2010-06-07 at 17:24 +0200, Dominick Grift wrote:
>> On Mon, Jun 07, 2010 at 10:56:08AM -0400, Christopher J. PeBenito wrote:
>>> On Mon, 2010-06-07 at 16:17 +0200, Dominick Grift wrote:
>>>> On Mon, Jun 07, 2010 at 10:00:08AM -0400, Christopher J. PeBenito wrote:
>>>>> On Mon, 2010-06-07 at 14:57 +0200, Dominick Grift wrote:
>>>>>> On Mon, Jun 07, 2010 at 08:49:09AM -0400, Christopher J. PeBenito wrote:
>>>>>>> On Fri, 2010-06-04 at 09:41 -0400, Daniel J Walsh wrote:
>>>>>>>> On 06/04/2010 09:34 AM, Christopher J. PeBenito wrote:
>>>>>>>>> On Wed, 2010-06-02 at 16:23 -0400, Daniel J Walsh wrote:
>>>>>>>>>> http://people.fedoraproject.org/~dwalsh/SELinux/F14/kernel_filesystem.patch
>>>>>>>>>>
>>>>>>>>>> Changes for /cgroup policy
>>>>>>>>>
>>>>>>>>> While moving the labeling of cgroup from kernel to filesystem modules
>>>>>>>>> may make sense, I'm not sure why the type and interfaces need to be
>>>>>>>>> renamed.
>>>>>>>>>
>>>>>>>> Well it is a file system?
>>>>>>>
>>>>>>> Thats not necessarily a good reason, since other pseudo filesystems
>>>>>>> exist in other modules, for good reason.  It also doesn't explain the
>>>>>>> renaming.
>>>>>>
>>>>>> the libcgroup suite was one of the reasons to rename. libcgroup which
>>>>>> automates cgroup management installs the /cgroup mountpoint. whilst
>>>>>> that directories content is the cgroup pseudo filesystem. So we needed
>>>>>> two types for almost the same purpose. So we choose cgroup_t for
>>>>>> libcgroups /cgroup mountpoint and we decided to rename the cgroupfs
>>>>>> pseudo fs cgroupfs
>>>>>
>>>>> I don't see a need for two different types.
>>>>
>>>> I guess strictly speaking there is no need for two types. We can just
>>>> add the fc spec for /cgroup -d to filesystem.fc
>>>
>>> Thats what I had in mind.
>>
>> So.. you want cgroup_t instead of cgroupfs_t?
>
> Yes, since the filesystem is called cgroup and the cgroup_t type already
> exists to label it.
>
>> You realize that when we merge the two, that the chosen type will get
>> the mountpoint attribute even if its a directory under /cgroup?
>
> Yes.
>
I don't care either way.  Just want to get it settled.

  reply	other threads:[~2010-06-07 16:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 20:23 [refpolicy] kernel_filesystem.patch Daniel J Walsh
2010-06-04 13:34 ` Christopher J. PeBenito
2010-06-04 13:41   ` Daniel J Walsh
2010-06-07 12:49     ` Christopher J. PeBenito
2010-06-07 12:57       ` Dominick Grift
2010-06-07 14:00         ` Christopher J. PeBenito
2010-06-07 14:17           ` Dominick Grift
2010-06-07 14:56             ` Christopher J. PeBenito
2010-06-07 15:24               ` Dominick Grift
2010-06-07 15:41                 ` Christopher J. PeBenito
2010-06-07 16:50                   ` Daniel J Walsh [this message]
2010-06-04 15:59   ` Dominick Grift
  -- strict thread matches above, loose matches on Subject: below --
2010-08-26 23:18 Daniel J Walsh
2010-02-23 22:09 Daniel J Walsh
2010-03-12 16:41 ` Christopher J. PeBenito
2010-03-12 20:24   ` Daniel J Walsh
2010-03-12 20:52     ` Christopher J. PeBenito
2010-03-13 15:39       ` Dominick Grift
2010-03-13 18:17       ` Dominick Grift
2010-03-13 23:38         ` Chris PeBenito
2010-03-20 15:59           ` Dominick Grift
2010-03-22 13:49             ` Daniel J Walsh
2009-11-12 21:02 Daniel J Walsh
2009-11-23 18:16 ` Christopher J. PeBenito
2009-05-21 15:26 Daniel J Walsh
2009-06-08 17:17 ` Christopher J. PeBenito
2009-03-02 22:20 Daniel J Walsh
2009-03-04 16:16 ` Christopher J. PeBenito
2008-11-25 21:45 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=4C0D2350.5090004@redhat.com \
    --to=dwalsh@redhat.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.