From: Sergey Senozhatsky <senozhatsky@chromium.org>
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, laoar.shao@gmail.com,
kernel-team@meta.com, Bernd Schubert <bschubert@ddn.com>,
Tomasz Figa <tfiga@chromium.org>
Subject: Re: [PATCH RESEND v9 2/3] fuse: add optional kernel-enforced timeout for requests
Date: Wed, 4 Dec 2024 22:14:38 +0900 [thread overview]
Message-ID: <20241204131438.GA16709@google.com> (raw)
In-Reply-To: <20241114191332.669127-3-joannelkoong@gmail.com>
On (24/11/14 11:13), Joanne Koong wrote:
[..]
> @@ -920,6 +935,9 @@ struct fuse_conn {
> /** IDR for backing files ids */
> struct idr backing_files_map;
> #endif
> +
> + /** Only used if the connection enforces request timeouts */
> + struct fuse_timeout timeout;
> };
[..]
> @@ -749,6 +750,7 @@ static const struct fs_parameter_spec fuse_fs_parameters[] = {
> fsparam_u32 ("max_read", OPT_MAX_READ),
> fsparam_u32 ("blksize", OPT_BLKSIZE),
> fsparam_string ("subtype", OPT_SUBTYPE),
> + fsparam_u16 ("request_timeout", OPT_REQUEST_TIMEOUT),
> {}
> };
>
> @@ -844,6 +846,10 @@ static int fuse_parse_param(struct fs_context *fsc, struct fs_parameter *param)
> ctx->blksize = result.uint_32;
> break;
>
> + case OPT_REQUEST_TIMEOUT:
> + ctx->req_timeout = result.uint_16;
> + break;
> +
A quick question: so for this user-space should be updated
to request fuse-watchdog on particular connection? Would
it make sense to have a way to simply enforce watchdog on
all connections?
next prev parent reply other threads:[~2024-12-04 13:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 19:13 [PATCH RESEND v9 0/3] fuse: add kernel-enforced request timeout option Joanne Koong
2024-11-14 19:13 ` [PATCH RESEND v9 1/3] fs_parser: add fsparam_u16 helper Joanne Koong
2024-11-14 19:13 ` [PATCH RESEND v9 2/3] fuse: add optional kernel-enforced timeout for requests Joanne Koong
2024-11-28 10:44 ` Sergey Senozhatsky
2024-11-28 11:00 ` Bernd Schubert
2024-11-28 11:09 ` Sergey Senozhatsky
2024-11-28 11:23 ` Bernd Schubert
2024-11-28 11:54 ` Sergey Senozhatsky
2024-12-02 9:45 ` Tomasz Figa
2024-12-02 14:43 ` Bernd Schubert
2024-12-02 19:29 ` Joanne Koong
2024-12-03 4:31 ` Sergey Senozhatsky
2024-12-03 5:11 ` Joanne Koong
2024-12-04 14:40 ` Tomasz Figa
2024-12-04 14:51 ` Brian Geffon
2024-12-04 15:09 ` Bernd Schubert
2024-12-05 3:23 ` Sergey Senozhatsky
2024-12-05 11:07 ` Brian Geffon
2024-12-03 11:01 ` Sergey Senozhatsky
2024-12-06 0:06 ` Joanne Koong
2024-12-06 4:28 ` Sergey Senozhatsky
2024-12-04 13:14 ` Sergey Senozhatsky [this message]
2024-12-05 23:10 ` Joanne Koong
2024-12-04 13:47 ` Sergey Senozhatsky
2024-12-05 23:29 ` Joanne Koong
2024-12-06 3:26 ` Sergey Senozhatsky
2024-12-06 0:37 ` Jeff Layton
2024-12-06 19:19 ` Joanne Koong
2024-12-06 20:06 ` Jeff Layton
2024-12-06 16:30 ` Etienne Martineau
2024-12-06 19:05 ` Joanne Koong
2024-12-06 19:56 ` Etienne
2024-12-06 21:52 ` Joanne Koong
2024-12-06 20:12 ` Jeff Layton
2024-12-06 21:54 ` Joanne Koong
2024-11-14 19:13 ` [PATCH RESEND v9 3/3] fuse: add default_request_timeout and max_request_timeout sysctls Joanne Koong
2024-12-06 0:43 ` Jeff Layton
2024-12-06 18:16 ` Joanne Koong
2024-11-21 22:02 ` [PATCH RESEND v9 0/3] fuse: add kernel-enforced request timeout option Josef Bacik
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=20241204131438.GA16709@google.com \
--to=senozhatsky@chromium.org \
--cc=bernd.schubert@fastmail.fm \
--cc=bschubert@ddn.com \
--cc=jefflexu@linux.alibaba.com \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=laoar.shao@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=tfiga@chromium.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