From: Yafang Shao <laoar.shao@gmail.com>
To: miklos@szeredi.hu
Cc: linux-fsdevel@vger.kernel.org, Yafang Shao <laoar.shao@gmail.com>
Subject: [RFC PATCH 0/2] fuse: Add timeout support for fuse connection
Date: Wed, 24 Jul 2024 15:11:54 +0800 [thread overview]
Message-ID: <20240724071156.97188-1-laoar.shao@gmail.com> (raw)
Currently, when an issue arises within the FUSE daemon, the FUSE connection
can become indefinitely stuck. The only resolution currently available is
to manually abort the connection using the sysfs interface. However,
relying solely on the abort interface for automatic error handling is
unreliable. To address this, a timeout mechanism has been introduced in
this series. When the timeout is reached without receiving a response from
the FUSE daemon, the FUSE request will terminate with an error code
returned to the user space, enabling the user space to handle the situation
appropriately.
Furthermore, the timeout value is configurable by the user, allowing for
customization based on specific workload requirements.
Yafang Shao (2):
fuse: Add "timeout" sysfs attribute for each fuse connection
fuse: Enhance each fuse connection with timeout support
fs/fuse/control.c | 50 ++++++++++++++++++++++++++++++++++++++++-
fs/fuse/dev.c | 57 ++++++++++++++++++++++++++++++++++++++++-------
fs/fuse/fuse_i.h | 7 +++++-
3 files changed, 104 insertions(+), 10 deletions(-)
--
2.43.5
next reply other threads:[~2024-07-24 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 7:11 Yafang Shao [this message]
2024-07-24 7:11 ` [RFC PATCH 1/2] fuse: Add "timeout" sysfs attribute for each fuse connection Yafang Shao
2024-07-24 7:11 ` [RFC PATCH 2/2] fuse: Enhance each fuse connection with timeout support Yafang Shao
2024-07-24 17:09 ` Joanne Koong
2024-07-25 2:06 ` Yafang Shao
2024-07-25 17:56 ` 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=20240724071156.97188-1-laoar.shao@gmail.com \
--to=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).