From: The 8472 <kernel@infinite-source.de>
To: Antonio SJ Musumeci <trapexit@spawn.link>,
The 8472 <kernel@infinite-source.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: EBADF returned from close() by FUSE
Date: Sat, 20 Apr 2024 01:04:05 +0200 [thread overview]
Message-ID: <58766a27-e6ff-4d73-a7aa-625f3aa5f7d3@infinite-source.de> (raw)
In-Reply-To: <aaabfbe6-2c61-46dc-ab82-b8d555f30238@spawn.link>
On 20-04-2024 00:47, Antonio SJ Musumeci wrote:
> On 4/19/24 17:04, The 8472 wrote:
>> I'm writing to a linux mailing list, am I not? And referring to linux-specific
>> manpages, not the POSIX ones. The way the linux kernel chooses to pass
>> what FUSE sends to userspace is under its control.
>>
>> I would like linux to adhere more closely to its own API contract or improve its
>> documentation.
> And you're talking about FUSE which is a cross platform (Linux, FreeBSD,
> MacOS, Windows) protocol. And that protocol defacto includes what
> happens when the FUSE server returns and error. If Linux suddenly
> changes what happens when the server returns an error it will affect
> everyone.
If it is the official position that the whims of FUSE servers have
primacy over current kernel API guarantees then please update
the documentation of all affected syscalls and relax those
guarantees, similar to the note on the write(2) manpage.
next prev parent reply other threads:[~2024-04-19 23:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 22:10 EBADF returned from close() by FUSE The 8472
2024-04-19 3:30 ` Antonio SJ Musumeci
2024-04-19 6:55 ` The 8472
[not found] ` <8c7552b1-f371-4a75-98cc-f2c89816becb@spawn.link>
2024-04-19 18:18 ` The 8472
2024-04-19 20:07 ` Antonio SJ Musumeci
2024-04-19 20:45 ` The 8472
2024-04-19 21:29 ` Antonio SJ Musumeci
2024-04-19 22:04 ` The 8472
2024-04-19 22:47 ` Antonio SJ Musumeci
2024-04-19 23:04 ` The 8472 [this message]
2024-04-23 12:46 ` Miklos Szeredi
2024-04-23 13:24 ` Antonio SJ Musumeci
2024-04-23 13:38 ` Miklos Szeredi
[not found] ` <692a9f0b-9c2b-4850-b8bc-48f09fe41762@infinite-source.de>
2024-04-23 21:38 ` The 8472
2024-04-26 8:52 ` Miklos Szeredi
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=58766a27-e6ff-4d73-a7aa-625f3aa5f7d3@infinite-source.de \
--to=kernel@infinite-source.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trapexit@spawn.link \
/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).