linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <mszeredi@redhat.com>
To: Nikolaus Rath <Nikolaus@rath.org>
Cc: Mike Marshall <hubcap@omnibond.com>,
	Andrew Gallagher <andrewjcg@fb.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: commit d7afaec0b564f0609e116f5: fuse: add FUSE_NO_OPEN_SUPPORT flag to INIT
Date: Tue, 15 Nov 2016 14:33:22 +0100	[thread overview]
Message-ID: <CAOssrKcOe_Mbb4hLJ8CW0s5+8qRhMdy4AtsWuUzLAJ9qDEBxYw@mail.gmail.com> (raw)
In-Reply-To: <87d1i2j5af.fsf@thinkpad.rath.org>

On Fri, Nov 11, 2016 at 6:27 PM, Nikolaus Rath <Nikolaus@rath.org> wrote:

> Yeah, I'd expect most people to do that. But FUSE file systems are often
> a little more exotic and produce error conditions that don't match well
> with any of the codes documented in the manpages. If there is no good
> fit, I'd expect that most people would (as I have done so far) simply
> pick something more appropriate from errno(3). If some of these codes
> are forbidden (or only a subset allowed) I'd really like to document
> this. It's not reasonable to expect every libfuse user to start browsing
> the Linux VFS code to determine if they can use a particular error code.

The library and the kernel checks for -1000 < error <= 0.  There are
no other checks done by fuse.  However returning ENOSYS for open is
simply wrong, it's definitely not something a sane filesystem would
ever do.

Thanks,
Miklos

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 22:31 commit d7afaec0b564f0609e116f5: fuse: add FUSE_NO_OPEN_SUPPORT flag to INIT Nikolaus Rath
2016-11-10 23:12 ` Miklos Szeredi
2016-11-11  4:57   ` Nikolaus Rath
2016-11-11  8:43     ` Miklos Szeredi
2016-11-11 16:28       ` Nikolaus Rath
2016-11-11 16:53         ` Mike Marshall
2016-11-11 17:27           ` Nikolaus Rath
2016-11-11 17:53             ` Mike Marshall
2016-11-15 15:50               ` Nikolaus Rath
2016-11-15 13:33             ` Miklos Szeredi [this message]
2016-11-15 15:53               ` Nikolaus Rath

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=CAOssrKcOe_Mbb4hLJ8CW0s5+8qRhMdy4AtsWuUzLAJ9qDEBxYw@mail.gmail.com \
    --to=mszeredi@redhat.com \
    --cc=Nikolaus@rath.org \
    --cc=andrewjcg@fb.com \
    --cc=hubcap@omnibond.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).