From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@lst.de>
Cc: trond.myklebust@primarydata.com, jlayton@poochiereds.net,
schumaker.anna@gmail.com, linux-nfs@vger.kernel.org
Subject: Re: open by handle support for NFS V2
Date: Thu, 29 Jun 2017 11:46:50 -0400 [thread overview]
Message-ID: <20170629154650.GC1651@fieldses.org> (raw)
In-Reply-To: <20170629133453.19641-1-hch@lst.de>
On Thu, Jun 29, 2017 at 06:34:49AM -0700, Christoph Hellwig wrote:
> this resurrects parts of an old series to add open by handle support to
> NFS. The prime intent here is to support the actual open by handle
> ioctls, although it will also allow very crude re-exporting. Without
> the other patches from Jeff's series that re-exporting will suck badly
> though.
Why do we want this?
Any re-export support is going to have some major limitations. (No file
locking, and re-export of NFSv4 probably not possible?)
Last I heard the only motivation was extremely specific to Primary
Data's setup. I'm happy to help them, but I think we need *some*
evidence this will be useful to upstream users.
--b.
next prev parent reply other threads:[~2017-06-29 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 13:34 open by handle support for NFS V2 Christoph Hellwig
2017-06-29 13:34 ` [PATCH 1/4] nfs: replace d_add with d_splice_alias in atomic_open Christoph Hellwig
2017-06-29 13:34 ` [PATCH 2/4] nfs: add a nfs_ilookup helper Christoph Hellwig
2017-06-29 13:34 ` [PATCH 3/4] nfs4: add NFSv4 LOOKUPP handlers Christoph Hellwig
2017-06-29 13:34 ` [PATCH 4/4] nfs: add export operations Christoph Hellwig
2017-06-29 15:46 ` J. Bruce Fields [this message]
2017-06-30 17:00 ` open by handle support for NFS V2 Trond Myklebust
2017-06-30 17:38 ` bfields
2017-07-01 9:34 ` Mkrtchyan, Tigran
2017-07-01 12:17 ` J. Bruce Fields
2017-07-03 6:39 ` DENIEL Philippe
2017-07-07 2:41 ` NeilBrown
2017-07-07 3:19 ` Trond Myklebust
2017-07-07 4:27 ` NeilBrown
2017-07-17 12:02 ` Jeff Layton
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=20170629154650.GC1651@fieldses.org \
--to=bfields@fieldses.org \
--cc=hch@lst.de \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
--cc=schumaker.anna@gmail.com \
--cc=trond.myklebust@primarydata.com \
/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.