linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, NeilBrown <neilb@suse.de>,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	miklos@szeredi.hu, viro@zeniv.linux.org.uk, haveblue@us.ibm.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, hch@infradead.org,
	linux-security-module@vger.kernel.org
Subject: Re: r-o bind in nfsd
Date: Thu, 27 Mar 2008 08:35:03 +1100 (EST)	[thread overview]
Message-ID: <Xine.LNX.4.64.0803270834070.1952@us.intercode.com.au> (raw)
In-Reply-To: <20080326164753.GA20578@sergelap.ibm.com>

On Wed, 26 Mar 2008, Serge E. Hallyn wrote:

> Not only that, but containers require an LSM to provide user isolation
> and root containment.

You mean LSM hooks, which various LSM could utilize if desired, right?


- James
-- 
James Morris
<jmorris@namei.org>

  reply	other threads:[~2008-03-26 21:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 14:59 r-o bind in nfsd Miklos Szeredi
2008-03-21 15:54 ` Al Viro
2008-03-21 16:24   ` Miklos Szeredi
2008-03-21 16:35     ` Al Viro
2008-03-21 16:54       ` Miklos Szeredi
2008-03-21 17:08         ` Miklos Szeredi
2008-03-21 18:11           ` Al Viro
2008-03-21 18:52             ` Miklos Szeredi
2008-03-21 19:49               ` Al Viro
2008-03-21 20:23                 ` Miklos Szeredi
2008-03-22  2:20                   ` Tetsuo Handa
2008-03-21 21:08               ` Dave Hansen
2008-03-21 21:17                 ` Miklos Szeredi
2008-03-25  2:52         ` Neil Brown
2008-03-25 11:45           ` Tetsuo Handa
2008-03-25 22:32             ` NeilBrown
     [not found]               ` <20080325224919.GM10722@ZenIV.linux.org.uk>
2008-03-25 23:29                 ` NeilBrown
2008-03-26 12:04               ` Stephen Smalley
2008-03-26 16:47                 ` Serge E. Hallyn
2008-03-26 21:35                   ` James Morris [this message]
2008-03-27  0:29                     ` 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.0803270834070.1952@us.intercode.com.au \
    --to=jmorris@namei.org \
    --cc=akpm@linux-foundation.org \
    --cc=haveblue@us.ibm.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neilb@suse.de \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=sds@tycho.nsa.gov \
    --cc=serue@us.ibm.com \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).