From: Al Viro <viro@ZenIV.linux.org.uk>
To: Emily Maier <emily@emilymaier.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fuse: Expose read from directory to userspace
Date: Fri, 22 Apr 2016 14:23:56 +0100 [thread overview]
Message-ID: <20160422132356.GJ25498@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1461329404-7967-1-git-send-email-emily@emilymaier.net>
On Fri, Apr 22, 2016 at 08:50:04AM -0400, Emily Maier wrote:
> The VFS permits filesystems to implement read(2) on directories, but
> FUSE unconditionally returns -EISDIR for it. Expose this to userspace as
> FUSE_DIR_READ and continue returning the old behavior if the filesystem
> doesn't implement it.
What the hell for? read() on directories had been an anachronism since
early 80s, has nothing resembling a sane semantics, etc.
Why would we want to implement that idiocy?
next prev parent reply other threads:[~2016-04-22 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 12:50 [PATCH] fuse: Expose read from directory to userspace Emily Maier
2016-04-22 13:23 ` Al Viro [this message]
2016-04-24 4:57 ` Emily Maier
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=20160422132356.GJ25498@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=emily@emilymaier.net \
--cc=linux-fsdevel@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).