From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Reconsidering exportable UBIFS
Date: Mon, 18 Apr 2016 12:04:26 +0300 [thread overview]
Message-ID: <1460970266.7369.3.camel@gmail.com> (raw)
In-Reply-To: <5702E7F5.1050807@nod.at>
On Tue, 2016-04-05 at 00:17 +0200, Richard Weinberger wrote:
> The biggest problem I see is that UBIFS does not really support
> telldir()
> and seekdir().
> Directory offsets in UBIFS are plain hash values, so
> telldir()/seekdir() won't
> correctly work if UBIFS faces hash collisions.
> Currently UBIFS implements a hack which stores the UBIFS dent object
> into
> file->private_data such that consecutive readdir()s are guaranteed to
> work.
> A comment on UBIFS's readdir states:
> * This means that UBIFS cannot support NFS which requires full
> * 'seekdir()'/'telldir()' support.
Richard, I do not remember much about NFS support. I can only say that
I never really put efforts into this, unfortunately.
Here is an old discussion which could give you some more hints:
http://marc.info/?l=linux-nfsv4&m=126480082613293&w=2
Artem.
next prev parent reply other threads:[~2016-04-18 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 22:17 Reconsidering exportable UBIFS Richard Weinberger
2016-04-18 9:04 ` Artem Bityutskiy [this message]
2016-05-08 22:18 ` NeilBrown
2016-05-08 23:25 ` Al Viro
2016-05-09 5:03 ` NeilBrown
2016-05-11 14:09 ` Richard Weinberger
2016-05-11 14:10 ` Richard Weinberger
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=1460970266.7369.3.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.