mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	daniel@hozac.com, lizf@cn.fujitsu.com,
	Pavel Emelyanov <xemul@openvz.org>, Greg KH <greg@kroah.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 1/1] cgroups: implement device whitelist (v6)
Date: Mon, 31 Mar 2008 09:00:53 -0500	[thread overview]
Message-ID: <20080331140053.GA9909@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20080329081839.GA4423@ucw.cz>

Quoting Pavel Machek (pavel@ucw.cz):
> On Wed 2008-03-26 13:05:43, Serge E. Hallyn wrote:
> > (This is identical to the version I sent on Mar 19 in response to
> > the comments by Daniel Hokka Zakrisson, which are the last
> > comments I've gotten.)
> > 
> > Implement a cgroup to track and enforce open and mknod restrictions on device
> > files.  A device cgroup associates a device access whitelist with each
> > cgroup.  A whitelist entry has 4 fields.  'type' is a (all), c (char), or
> > b (block).  'all' means it applies to all types and all major and minor
> > numbers.  Major and minor are either an integer or * for all.
> > Access is a composition of r (read), w (write), and m (mknod).
> > 
> > The root device cgroup starts with rwm to 'all'.  A child devcg gets
> > a copy of the parent.  Admins can then remove devices from the
> > whitelist or add new entries.  A child cgroup can never receive a
> > device access which is denied its parent.  However when a device
> > access is removed from a parent it will not also be removed from the
> > child(ren).
> > 
> > An entry is added using devices.allow, and removed using
> > devices.deny.  For instance
> > 
> > 	echo 'c 1:3 mr' > /cgroups/1/devices.allow
> > 
> > allows cgroup 1 to read and mknod the device usually known as
> > /dev/null.  Doing
> > 
> > 	echo a > /cgroups/1/devices.deny
> 
> Can't you use selinux or something?

No.  At the moment SELinux can't authorize based on type/major:minor.  I
would like to add that support later on, but even when I do, folks such
as the openvz folks do not want to rely on any security modules.

> Or just fix the userland as this is for old-udev compatibility, only?

Until the part of Miklos' user mounts patches go in which enforces MNT_NODEV
on mounts made by someone who is !capable(CAP_MKNOD), using capability bounding
sets is completely inadequate.

> The interface is ugly...

What's ugly about it?  How could we clean it up?

> > diff --git a/include/linux/cgroup_subsys.h b/include/linux/cgroup_subsys.h
> > index 1ddebfc..e287745 100644
> > --- a/include/linux/cgroup_subsys.h
> > +++ b/include/linux/cgroup_subsys.h
> > @@ -42,3 +42,9 @@ SUBSYS(mem_cgroup)
> >  #endif
> >  
> >  /* */
> > +
> > +#ifdef CONFIG_CGROUP_DEVICE
> > +SUBSYS(devices)
> > +#endif
> > +
> > +/* */
> 
> I don't know what this is, but it does not look like C...

Huh?

-serge

  reply	other threads:[~2008-03-31 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 18:05 Serge E. Hallyn
2008-03-27  9:04 ` Andrew Morton
2008-03-27  9:07   ` Li Zefan
2008-03-27 16:24   ` Serge E. Hallyn
2008-03-27 16:40     ` Paul Menage
2008-03-27 17:37       ` Serge E. Hallyn
2008-03-29  8:18 ` Pavel Machek
2008-03-31 14:00   ` Serge E. Hallyn [this message]
2008-04-01 12:32     ` Pavel Machek
2008-04-01 12:34       ` Alexey Dobriyan
2008-04-01 22:07       ` Serge E. Hallyn
  -- strict thread matches above, loose matches on Subject: below --
2008-03-19 20:56 Serge E. Hallyn

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=20080331140053.GA9909@sergelap.austin.ibm.com \
    --to=serue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=daniel@hozac.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=pavel@ucw.cz \
    --cc=xemul@openvz.org \
    /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

all inboxes | Powered by JetHome®