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, Greg KH <greg@kroah.com>,
Stephen Smalley <sds@epoch.ncsc.mil>,
Casey Schaufler <casey@schaufler-ca.com>,
Pavel Emelianov <xemul@openvz.org>
Subject: Re: [RFC] cgroups: implement device whitelist lsm (v2)
Date: Fri, 14 Mar 2008 00:50:51 +1100 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0803140049270.9059@us.intercode.com.au> (raw)
In-Reply-To: <20080313131818.GA9771@sergelap.austin.ibm.com>
On Thu, 13 Mar 2008, Serge E. Hallyn wrote:
> That does make for a simpler implementation at this point, however if
> any other such LSMs come along (as Casey seemed to think they would) the
> end result could end up being horrible spaghetti code of dependencies
> and interrelated configs.
That can be addressed as the need arises. A basic tenet of kernel
development is to avoid speculative infrastructure.
> But OTOH we went years with no such changes, so that's probably not a
> particularly practical concern unless someone can cite specific upcoming
> examples. So if noone objects I'll try that approach.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-03-13 13:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 3:27 [RFC] cgroups: implement device whitelist lsm (v2) Serge E. Hallyn
2008-03-13 9:25 ` James Morris
2008-03-13 13:18 ` Serge E. Hallyn
2008-03-13 13:50 ` James Morris [this message]
2008-03-13 14:38 ` Serge E. Hallyn
2008-03-13 22:27 ` James Morris
2008-03-13 22:46 ` Serge E. Hallyn
2008-03-13 23:49 ` James Morris
2008-03-14 1:41 ` Serge E. Hallyn
2008-03-14 4:47 ` Greg KH
2008-03-14 13:54 ` Serge E. Hallyn
2008-03-14 13:58 ` Pavel Emelyanov
2008-03-14 15:45 ` Serge E. Hallyn
2008-03-14 15:54 ` Pavel Emelyanov
2008-03-14 16:57 ` Stephen Smalley
2008-03-14 9:28 ` Pavel Emelyanov
2008-03-14 13:58 ` Serge E. Hallyn
2008-03-14 14:05 ` Pavel Emelyanov
2008-03-14 14:37 ` Serge E. Hallyn
2008-03-14 15:07 ` Pavel Emelyanov
2008-03-14 14:12 ` Paul Menage
2008-03-14 14:42 ` Serge E. Hallyn
2008-03-16 0:59 ` Paul Menage
2008-03-14 2:51 ` Casey Schaufler
2008-03-14 9:16 ` Paul Menage
2008-03-14 14:05 ` Serge E. Hallyn
2008-03-14 14:15 ` Paul Menage
2008-03-14 14:35 ` Serge E. Hallyn
2008-03-16 0:57 ` Paul Menage
2008-03-14 9:18 ` Paul Menage
2008-03-14 14:00 ` 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=Xine.LNX.4.64.0803140049270.9059@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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.