From: James Morris <jmorris@namei.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Linux Containers <containers@lists.osdl.org>,
Stephen Smalley <sds@epoch.ncsc.mil>,
Pavel Emelianov <xemul@openvz.org>, Greg KH <greg@kroah.com>,
Casey Schaufler <casey@schaufler-ca.com>,
Paul Menage <menage@google.com>
Subject: Re: [PATCH] cgroups: implement device whitelist (v4)
Date: Tue, 18 Mar 2008 15:17:53 +1100 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0803181517260.1898@us.intercode.com.au> (raw)
In-Reply-To: <20080317180722.GA17111@sergelap.austin.ibm.com>
On Mon, 17 Mar 2008, Serge E. Hallyn wrote:
> 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).
Acked-by: James Morris <jmorris@namei.org>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-03-18 4:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 18:07 [PATCH] cgroups: implement device whitelist (v4) Serge E. Hallyn
2008-03-18 4:17 ` James Morris [this message]
[not found] ` <20080317180722.GA17111-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-03-18 5:15 ` Li Zefan
2008-03-18 5:15 ` Li Zefan
2008-03-18 14:10 ` Serge E. Hallyn
2008-03-18 7:57 ` Pavel Emelyanov
2008-03-18 7:57 ` Pavel Emelyanov
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=Xine.LNX.4.64.0803181517260.1898@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=containers@lists.osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=menage@google.com \
--cc=sds@epoch.ncsc.mil \
--cc=serue@us.ibm.com \
--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 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.