public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: James Morris <jmorris@redhat.com>
Cc: Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] fork historic module
Date: Fri, 17 Dec 2004 10:43:55 -0800	[thread overview]
Message-ID: <20041217104355.A469@build.pdx.osdl.net> (raw)
In-Reply-To: <Xine.LNX.4.44.0412171134220.14531-100000@thoron.boston.redhat.com>; from jmorris@redhat.com on Fri, Dec 17, 2004 at 11:40:18AM -0500

* James Morris (jmorris@redhat.com) wrote:
> 
> > Any comments and suggestions are welcome.
> 
> I don't see why you are using LSM for this.
> 
> It's not an access control system, only uses one LSM hook (I gather
> becuase it happens to be in the right place), and furthermore, uses a hook
> intended for LSM resource management.

We went through this before.  I recommended against using it, and
suggested using proper framework, such as PAGG or CKRM.  However,
Guillaume preferred to use something that was in the kernel instead of
relying on another external patch.  I don't have a problem with that,
but it's not mergeable.  Ideally efforts would be made to consolidate to
common resource management needs, and elsa could be part of this effort.
So Guillame, feel free to use the LSM hook, but just know it's not a
mergeable work.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2004-12-17 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a482d6bf04121708146f221b15@mail.gmail.com>
2004-12-17 16:40 ` [RFC] fork historic module James Morris
2004-12-17 18:43   ` Chris Wright [this message]
2004-12-17 14:58 Guillaume Thouvenin
2004-12-17 15:24 ` David Vrabel
2004-12-17 17:06   ` Randy.Dunlap

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=20041217104355.A469@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=guillaume.thouvenin@bull.net \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.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