From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christopher T Vogan <cvogan@us.ibm.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: What is NFSv4 READDIR doesn't return a filehandle....
Date: Thu, 21 Mar 2013 09:47:29 -0400 [thread overview]
Message-ID: <20130321134729.GC27838@fieldses.org> (raw)
In-Reply-To: <OF5A466E86.6A319FE3-ON87257B34.007C6188-86257B34.007C87C8@us.ibm.com>
On Wed, Mar 20, 2013 at 05:40:11PM -0500, Christopher T Vogan wrote:
> This condition is easily recoverable, as ANY missing attribute on a
> readdir
> is with a lookup/readdir.
By the same token, the server can just as well recover by doing that
extra lookup itself, can't it? (That's more-or-less how the Linux
server gets attributes on readdir.)
Understood that it can be a pain (the Linux server's readdir
implementation has needed some minor surgery over the years to get this
right), but I do think it's the server's responsibility....
--b.
> Our decision to not return the FH on a readdir
> reply under certain narrow conditions is not one of convenience but of
> limitations of some underlying filesystem types, and if "convenience" is
> to be used as an accusative, it can easily be returned to the client's
> refusal to deal with the legal withholding of an attribute on a readdir
> reply.
next prev parent reply other threads:[~2013-03-21 13:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 22:40 What is NFSv4 READDIR doesn't return a filehandle Christopher T Vogan
2013-03-20 23:48 ` Myklebust, Trond
2013-03-20 23:53 ` Haynes, Tom
2013-03-21 0:33 ` Myklebust, Trond
2013-03-21 1:41 ` [nfsv4] " Rick Macklem
2013-03-21 2:04 ` Myklebust, Trond
2013-03-21 2:37 ` Myklebust, Trond
2013-03-21 3:38 ` Rick Macklem
2013-03-21 4:04 ` Myklebust, Trond
2013-03-21 13:37 ` J. Bruce Fields
2013-03-21 14:15 ` Rick Macklem
2013-03-21 4:04 ` Rick Macklem
2013-03-21 13:47 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-16 23:05 NeilBrown
2012-09-17 12:51 ` Myklebust, Trond
2012-09-18 2:04 ` NeilBrown
2012-09-21 2:44 ` Myklebust, Trond
2012-09-24 0:41 ` Jeff Layton
2012-09-24 1:53 ` Myklebust, Trond
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=20130321134729.GC27838@fieldses.org \
--to=bfields@fieldses.org \
--cc=cvogan@us.ibm.com \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).