From: Yafang Shao <laoar.shao@gmail.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org,
josef@toxicpanda.com, bernd.schubert@fastmail.fm,
jefflexu@linux.alibaba.com, kernel-team@meta.com
Subject: Re: [PATCH v3 0/2] fuse: add timeout option for requests
Date: Mon, 12 Aug 2024 10:33:03 +0800 [thread overview]
Message-ID: <CALOAHbCOBy66VQVBax4BEnGaadaq3x=8_GSBc2OXJQ1WOntvkw@mail.gmail.com> (raw)
In-Reply-To: <20240808190110.3188039-1-joannelkoong@gmail.com>
On Fri, Aug 9, 2024 at 3:02 AM Joanne Koong <joannelkoong@gmail.com> wrote:
>
> There are situations where fuse servers can become unresponsive or take
> too long to reply to a request. Currently there is no upper bound on
> how long a request may take, which may be frustrating to users who get
> stuck waiting for a request to complete.
>
> This patchset adds a timeout option for requests and two dynamically
> configurable fuse sysctls "default_request_timeout" and "max_request_timeout"
> for controlling/enforcing timeout behavior system-wide.
>
> Existing fuse servers will not be affected unless they explicitly opt into the
> timeout.
>
> v2: https://lore.kernel.org/linux-fsdevel/20240730002348.3431931-1-joannelkoong@gmail.com/
> Changes from v2:
> - Disarm / rearm timer in dev_do_read to handle race conditions (Bernrd)
> - Disarm timer in error handling for fatal interrupt (Yafang)
> - Clean up do_fuse_request_end (Jingbo)
> - Add timer for notify retrieve requests
> - Fix kernel test robot errors for #define no-op functions
>
> v1: https://lore.kernel.org/linux-fsdevel/20240717213458.1613347-1-joannelkoong@gmail.com/
> Changes from v1:
> - Add timeout for background requests
> - Handle resend race condition
> - Add sysctls
>
>
> Joanne Koong (2):
> fuse: add optional kernel-enforced timeout for requests
> fuse: add default_request_timeout and max_request_timeout sysctls
>
> Documentation/admin-guide/sysctl/fs.rst | 17 ++
> fs/fuse/Makefile | 2 +-
> fs/fuse/dev.c | 197 +++++++++++++++++++++++-
> fs/fuse/fuse_i.h | 30 ++++
> fs/fuse/inode.c | 24 +++
> fs/fuse/sysctl.c | 42 +++++
> 6 files changed, 303 insertions(+), 9 deletions(-)
> create mode 100644 fs/fuse/sysctl.c
>
> --
> 2.43.5
>
Hello Joanne,
I have tested this version, and the crash no longer occurs. Thanks for
the update.
--
Regards
Yafang
next prev parent reply other threads:[~2024-08-12 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 19:01 [PATCH v3 0/2] fuse: add timeout option for requests Joanne Koong
2024-08-08 19:01 ` [PATCH v3 1/2] fuse: add optional kernel-enforced timeout " Joanne Koong
2024-08-08 20:50 ` Josef Bacik
2024-08-09 14:14 ` Josef Bacik
2024-08-09 18:33 ` Joanne Koong
2024-08-09 6:22 ` Jingbo Xu
2024-08-09 17:51 ` Joanne Koong
2024-08-13 17:04 ` Bernd Schubert
2024-08-13 18:38 ` Joanne Koong
2024-08-08 19:01 ` [PATCH v3 2/2] fuse: add default_request_timeout and max_request_timeout sysctls Joanne Koong
2024-08-08 20:50 ` Josef Bacik
2024-08-13 20:28 ` Bernd Schubert
2024-08-12 2:33 ` Yafang Shao [this message]
2024-08-12 23:18 ` [PATCH v3 0/2] fuse: add timeout option for requests Joanne Koong
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='CALOAHbCOBy66VQVBax4BEnGaadaq3x=8_GSBc2OXJQ1WOntvkw@mail.gmail.com' \
--to=laoar.shao@gmail.com \
--cc=bernd.schubert@fastmail.fm \
--cc=jefflexu@linux.alibaba.com \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).