linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: "linux-nfs\@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: ELOOP from getdents
Date: Wed, 13 Jul 2016 17:06:34 +0200	[thread overview]
Message-ID: <87d1mh1ssl.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <E35BAE5E-4D9B-44B4-98B3-54BA36AC895B@primarydata.com> (Trond Myklebust's message of "Tue, 12 Jul 2016 23:26:00 +0000")

On Jul 12 2016, Trond Myklebust <trondmy@primarydata.com> wrote:
> In NFSv4, offsets 1 and 2 are reserved:
> https://tools.ietf.org/html/rfc7530#section-16.24

Ah, that explains it. Thanks!

I was assuming that I could export any "proper" unix file system over
NFS - and as far as I know, the rest of the VFS does not make any
assumptions (or reservations) about readdir offsets. Are there other
such constraints? I looked at the RFC, but it's rather hard to extract
that specific information...

Best,
Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

  parent reply	other threads:[~2016-07-13 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 20:36 ELOOP from getdents Nikolaus Rath
2016-07-12 22:35 ` Nikolaus Rath
2016-07-12 23:26   ` Trond Myklebust
2016-07-13 14:45     ` J. Bruce Fields
2016-07-13 15:06     ` Nikolaus Rath [this message]
2016-07-13 15:34       ` J. Bruce Fields

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=87d1mh1ssl.fsf@thinkpad.rath.org \
    --to=nikolaus@rath.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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 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).