All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.de>
Cc: Steve Dickson <SteveD@redhat.com>, NFS <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH/RFC nfs-utils] exports.man: improve documentation of 'nohide' and 'crossmnt'
Date: Tue, 17 Feb 2015 20:54:32 -0500	[thread overview]
Message-ID: <20150218015432.GA4148@fieldses.org> (raw)
In-Reply-To: <20150218124101.0c1cebfe@notabene.brown>

On Wed, Feb 18, 2015 at 12:41:01PM +1100, NeilBrown wrote:
> On Mon, 16 Feb 2015 15:17:51 -0500 bfields@fieldses.org (J. Bruce Fields)
> wrote:
> 
> > On Mon, Feb 16, 2015 at 12:21:07PM +1100, NeilBrown wrote:
> > > 
> > > 
> > > - note that 'nohide' is irrelevant for NFSv4
> > > - note that children on a 'crossmnt' filesystem cannot be unexported
> > > - note that 'nocrossmnt' is a valid option, but probably not useful.
> > > 
> > > Signed-off-by: NeilBrown <neilb@suse.de>
> > > 
> > > ---
> > > 
> > > I wonder if we should add a new option, e.g. "noaccess" so that children
> > > of a "crossmnt" filesystem can be hidden.  The  kernel wouldn't need to
> > > know about this.  It would just tell mountd to refuse to export that
> > > filesystem even if the parent was "crossmnt".
> > > ??
> > 
> > Seems logical enough, but I can't recall seeing requests for it, and
> > the options here already seem complicated enough.
> 
> I haven't seem requests myself.  Just rumours of 'nohide' not working with
> NFSv4, which seems to suggest that someone wants something like that.
> But I cannot find a clear source.
> 
> Maybe:
> 
> http://ubuntuforums.org/showthread.php?t=2152643
> http://ubuntuforums.org/showthread.php?t=1603881
> 
> 
> > 
> > In theory something like that could also be done with namespaces.  (So,
> > run mountd in a separate mount namespace that lacks those children.)
> 
> Do any of the NFS man pages need to be updated to say something about
> namespaces?

Maybe just a note in the rpc.mountd man page that export paths are all
with respect to the mount namespace rpc.mountd is running in?

--b.

  reply	other threads:[~2015-02-18  1:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16  1:21 [PATCH/RFC nfs-utils] exports.man: improve documentation of 'nohide' and 'crossmnt' NeilBrown
2015-02-16 20:17 ` J. Bruce Fields
2015-02-16 23:06   ` Trond Myklebust
2015-02-18  1:42     ` NeilBrown
2015-02-18  1:41   ` NeilBrown
2015-02-18  1:54     ` J. Bruce Fields [this message]
2015-02-18  2:09       ` NeilBrown
2015-02-18  2:54         ` J. Bruce Fields
2015-02-26 19:37 ` Steve Dickson

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=20150218015432.GA4148@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.