From: Miklos Szeredi <miklos@szeredi.hu>
To: Bernd Schubert <bschubert@ddn.com>
Cc: linux-fsdevel@vger.kernel.org, dsingh@ddn.com,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH v2 4/5] fuse: prepare for failing open response
Date: Fri, 2 Feb 2024 16:55:35 +0100 [thread overview]
Message-ID: <CAJfpeguYDpLN9xPycd7UMwJfp-mctc38e4KFr2v_CvPSDayxEQ@mail.gmail.com> (raw)
In-Reply-To: <20240131230827.207552-5-bschubert@ddn.com>
On Thu, 1 Feb 2024 at 00:09, Bernd Schubert <bschubert@ddn.com> wrote:
>
> From: Amir Goldstein <amir73il@gmail.com>
>
> In preparation for inode io modes, a server open response could fail
> due to conflicting inode io modes.
>
> Allow returning an error from fuse_finish_open() and handle the error in
> the callers. fuse_dir_open() can now call fuse_sync_release(), so handle
> the isdir case correctly.
Another question: will fuse_finish_open() fail for any reason other
than due to an interrupted wait?
If not, then maybe this belongs into a separate update which deals
with killability/interruptibility in a comprehensive way.
Thanks,
Miklos
next prev parent reply other threads:[~2024-02-02 15:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 23:08 [PATCH v2 0/5] fuse: inode IO modes and mmap Bernd Schubert
2024-01-31 23:08 ` [PATCH v2 1/5] fuse: Fix VM_MAYSHARE and direct_io_allow_mmap Bernd Schubert
2024-02-01 8:45 ` Miklos Szeredi
2024-02-01 14:36 ` Bernd Schubert
2024-02-01 14:52 ` Miklos Szeredi
2024-02-01 15:39 ` Bernd Schubert
2024-02-01 15:43 ` Miklos Szeredi
2024-02-01 15:48 ` Amir Goldstein
2024-02-01 16:16 ` Bernd Schubert
2024-02-02 14:47 ` Bernd Schubert
2024-01-31 23:08 ` [PATCH v2 2/5] fuse: Create helper function if DIO write needs exclusive lock Bernd Schubert
2024-02-06 9:20 ` Jingbo Xu
2024-02-07 13:38 ` Bernd Schubert
2024-02-07 13:44 ` Jingbo Xu
2024-02-07 14:13 ` Bernd Schubert
2024-02-08 0:04 ` Jingbo Xu
2024-01-31 23:08 ` [PATCH v2 3/5] fuse: Add fuse_dio_lock/unlock helper functions Bernd Schubert
2024-01-31 23:08 ` [PATCH v2 4/5] fuse: prepare for failing open response Bernd Schubert
2024-02-01 9:23 ` Miklos Szeredi
2024-02-01 10:16 ` Amir Goldstein
2024-02-01 10:28 ` Miklos Szeredi
2024-02-01 10:41 ` Amir Goldstein
2024-02-01 10:51 ` Miklos Szeredi
2024-02-01 16:46 ` Amir Goldstein
2024-02-02 12:03 ` Amir Goldstein
2024-02-02 15:49 ` Miklos Szeredi
2024-02-02 15:55 ` Miklos Szeredi [this message]
2024-02-02 16:07 ` Amir Goldstein
2024-01-31 23:08 ` [PATCH v2 5/5] fuse: introduce inode io modes Bernd Schubert
2024-02-01 14:47 ` Miklos Szeredi
2024-02-01 16:33 ` Amir Goldstein
2024-02-01 17:53 ` Bernd Schubert
2024-02-02 19:40 ` Amir Goldstein
2024-02-06 12:39 ` Amir Goldstein
2024-02-06 12:53 ` Miklos Szeredi
2024-02-06 13:07 ` Amir Goldstein
2024-02-01 10:30 ` [PATCH v2 0/5] fuse: inode IO modes and mmap Amir Goldstein
2024-02-01 14:30 ` Bernd Schubert
2024-02-01 15:56 ` Amir Goldstein
2024-02-01 16:01 ` Bernd Schubert
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=CAJfpeguYDpLN9xPycd7UMwJfp-mctc38e4KFr2v_CvPSDayxEQ@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=amir73il@gmail.com \
--cc=bschubert@ddn.com \
--cc=dsingh@ddn.com \
--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).