From: "Zhao Chen" <winters.zc@antgroup.com>
To: linux-fsdevel@vger.kernel.org
Cc: miklos@szeredi.hu
Subject: [PATCH v4 0/2] fuse: Add support for resend pending requests
Date: Tue, 09 Jan 2024 17:24:41 +0800 [thread overview]
Message-ID: <20240109092443.519460-1-winters.zc@antgroup.com> (raw)
After the FUSE daemon crashes, the fuse mount point becomes inaccessible.
In some production environments, a watchdog daemon is used to preserve
the FUSE connection's file descriptor (fd). When the FUSE daemon crashes,
a new FUSE daemon is started and takes over the fd from the watchdog
daemon, allowing it to continue providing services.
However, if any inflight requests are lost during the crash, the user
process becomes stuck as it does not receive any replies.
To resolve this issue, this patchset introduces a new notification type
that enable resending these pending requests to the FUSE daemon again,
allowing the stuck user process to recover.
When using the resend API, FUSE daemon needs to ensure avoidance of
processing duplicate non-idempotent requests to prevent potential
consistency issues. The high bit of the fuse request id is utilized for
indicating the resend request.
---
v3->v4:
- remove the code related to fpq->io
v2->v3:
- use notification instead of sysfs API to trigger resend
- simplify FUSE_REQ_ID_MASK related code
- rename some related macro names
v1->v2:
- remove flush sysfs API in the original mail
- add using high bit of request ID for indicating resend requests
- add wakeup in fuse_resend_pqueue()
Zhao Chen (2):
fuse: Introduce a new notification type for resend pending requests
fuse: Use the high bit of request ID for indicating resend requests
fs/fuse/dev.c | 61 ++++++++++++++++++++++++++++++++++++++-
fs/fuse/inode.c | 3 +-
include/uapi/linux/fuse.h | 12 ++++++++
3 files changed, 74 insertions(+), 2 deletions(-)
--
2.32.0.3.g01195cf9f
next reply other threads:[~2024-01-09 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 9:24 Zhao Chen [this message]
2024-01-09 9:24 ` [PATCH v4 1/2] fuse: Introduce a new notification type for resend pending requests Zhao Chen
2024-01-25 11:43 ` Jingbo Xu
2024-01-09 9:24 ` [PATCH v4 2/2] fuse: Use the high bit of request ID for indicating resend requests Zhao Chen
2024-03-05 15:29 ` [PATCH v4 0/2] fuse: Add support for resend pending requests 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=20240109092443.519460-1-winters.zc@antgroup.com \
--to=winters.zc@antgroup.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).