From: Joanne Koong <joannelkoong@gmail.com>
To: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org
Cc: josef@toxicpanda.com, bernd.schubert@fastmail.fm,
laoar.shao@gmail.com, kernel-team@meta.com
Subject: [PATCH v2 0/2] fuse: add timeout option for requests
Date: Mon, 29 Jul 2024 17:23:46 -0700 [thread overview]
Message-ID: <20240730002348.3431931-1-joannelkoong@gmail.com> (raw)
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.
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 | 187 +++++++++++++++++++++++-
fs/fuse/fuse_i.h | 30 ++++
fs/fuse/inode.c | 24 +++
fs/fuse/sysctl.c | 42 ++++++
6 files changed, 293 insertions(+), 9 deletions(-)
create mode 100644 fs/fuse/sysctl.c
--
2.43.0
next reply other threads:[~2024-07-30 0:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 0:23 Joanne Koong [this message]
2024-07-30 0:23 ` [PATCH v2 1/2] fuse: add optional kernel-enforced timeout for requests Joanne Koong
2024-08-04 22:46 ` Bernd Schubert
2024-08-05 4:45 ` Joanne Koong
2024-08-05 13:05 ` Bernd Schubert
2024-08-05 4:52 ` Joanne Koong
2024-08-05 13:26 ` Bernd Schubert
2024-08-05 22:10 ` Joanne Koong
2024-08-06 15:43 ` Bernd Schubert
2024-08-06 17:08 ` Joanne Koong
2024-08-05 7:32 ` Jingbo Xu
2024-08-05 22:53 ` Joanne Koong
2024-08-06 2:45 ` Jingbo Xu
2024-08-06 16:43 ` Joanne Koong
2024-08-06 15:50 ` Bernd Schubert
2024-07-30 0:23 ` [PATCH v2 2/2] fuse: add default_request_timeout and max_request_timeout sysctls Joanne Koong
2024-07-30 7:49 ` kernel test robot
2024-07-30 9:14 ` kernel test robot
2024-08-05 7:38 ` Jingbo Xu
2024-08-06 1:26 ` Joanne Koong
2024-07-30 5:59 ` [PATCH v2 0/2] fuse: add timeout option for requests Yafang Shao
2024-07-30 18:16 ` Joanne Koong
2024-07-31 2:13 ` Yafang Shao
2024-07-31 17:52 ` Joanne Koong
2024-07-31 18:46 ` Joanne Koong
2024-08-01 2:47 ` Yafang Shao
2024-08-02 19:05 ` Joanne Koong
2024-08-04 7:46 ` Yafang Shao
2024-08-05 5:05 ` Joanne Koong
2024-08-06 16:23 ` Joanne Koong
2024-08-06 17:11 ` Bernd Schubert
2024-08-06 18:26 ` Joanne Koong
2024-08-06 18:37 ` Joanne Koong
2024-08-06 20:08 ` 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=20240730002348.3431931-1-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=bernd.schubert@fastmail.fm \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=laoar.shao@gmail.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).