From: Bernd Schubert <[email protected]>
To: Miklos Szeredi <[email protected]>
Cc: Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>,
[email protected], [email protected],
Joanne Koong <[email protected]>,
Josef Bacik <[email protected]>,
Amir Goldstein <[email protected]>,
Ming Lei <[email protected]>, David Wei <[email protected]>,
[email protected], Luis Henriques <[email protected]>,
Bernd Schubert <[email protected]>
Subject: [PATCH v10 16/17] fuse: block request allocation until io-uring init is complete
Date: Mon, 20 Jan 2025 02:29:09 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
From: Bernd Schubert <[email protected]>
Avoid races and block request allocation until io-uring
queues are ready.
This is a especially important for background requests,
as bg request completion might cause lock order inversion
of the typical queue->lock and then fc->bg_lock
fuse_request_end
spin_lock(&fc->bg_lock);
flush_bg_queue
fuse_send_one
fuse_uring_queue_fuse_req
spin_lock(&queue->lock);
Signed-off-by: Bernd Schubert <[email protected]>
---
fs/fuse/dev.c | 3 ++-
fs/fuse/dev_uring.c | 3 +++
fs/fuse/fuse_i.h | 3 +++
fs/fuse/inode.c | 2 ++
4 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
index 1b593b23f7b8c319ec38c7e726dabf516965500e..f002e8a096f97ba8b6e039309292942995c901c5 100644
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -76,7 +76,8 @@ void fuse_set_initialized(struct fuse_conn *fc)
static bool fuse_block_alloc(struct fuse_conn *fc, bool for_background)
{
- return !fc->initialized || (for_background && fc->blocked);
+ return !fc->initialized || (for_background && fc->blocked) ||
+ (fc->io_uring && !fuse_uring_ready(fc));
}
static void fuse_drop_waiting(struct fuse_conn *fc)
diff --git a/fs/fuse/dev_uring.c b/fs/fuse/dev_uring.c
index fcce03174ee18153d597e9cd1a2659b1c237e3eb..1249c7fd4d63692413d103e72eaa5e502188d3bc 100644
--- a/fs/fuse/dev_uring.c
+++ b/fs/fuse/dev_uring.c
@@ -957,6 +957,7 @@ static void fuse_uring_do_register(struct fuse_ring_ent *ent,
if (ready) {
WRITE_ONCE(fiq->ops, &fuse_io_uring_ops);
WRITE_ONCE(ring->ready, true);
+ wake_up_all(&fc->blocked_waitq);
}
}
}
@@ -1130,6 +1131,8 @@ int __maybe_unused fuse_uring_cmd(struct io_uring_cmd *cmd,
if (err) {
pr_info_once("FUSE_IO_URING_CMD_REGISTER failed err=%d\n",
err);
+ fc->io_uring = 0;
+ wake_up_all(&fc->blocked_waitq);
return err;
}
break;
diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h
index e71556894bc25808581424ec7bdd4afeebc81f15..886c3af2195892cb2ca0a171cd7b930b6e92484c 100644
--- a/fs/fuse/fuse_i.h
+++ b/fs/fuse/fuse_i.h
@@ -867,6 +867,9 @@ struct fuse_conn {
/* Use pages instead of pointer for kernel I/O */
unsigned int use_pages_for_kvec_io:1;
+ /* Use io_uring for communication */
+ unsigned int io_uring;
+
/** Maximum stack depth for passthrough backing files */
int max_stack_depth;
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 328797b9aac9a816a4ad2c69b6880dc6ef6222b0..e9db2cb8c150878634728685af0fa15e7ade628f 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -1390,6 +1390,8 @@ static void process_init_reply(struct fuse_mount *fm, struct fuse_args *args,
else
ok = false;
}
+ if (flags & FUSE_OVER_IO_URING && fuse_uring_enabled())
+ fc->io_uring = 1;
} else {
ra_pages = fc->max_read / PAGE_SIZE;
fc->no_lock = 1;
--
2.43.0
next prev parent reply other threads:[~2025-01-20 1:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 1:28 [PATCH v10 00/17] fuse: fuse-over-io-uring Bernd Schubert
2025-01-20 1:28 ` [PATCH v10 01/17] fuse: rename to fuse_dev_end_requests and make non-static Bernd Schubert
2025-01-20 1:28 ` [PATCH v10 02/17] fuse: Move fuse_get_dev to header file Bernd Schubert
2025-01-20 1:28 ` [PATCH v10 03/17] fuse: Move request bits Bernd Schubert
2025-01-20 1:28 ` [PATCH v10 04/17] fuse: Add fuse-io-uring design documentation Bernd Schubert
2025-01-20 1:28 ` [PATCH v10 05/17] fuse: make args->in_args[0] to be always the header Bernd Schubert
2025-01-20 1:28 ` [PATCH v10 06/17] fuse: {io-uring} Handle SQEs - register commands Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 07/17] fuse: Make fuse_copy non static Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 08/17] fuse: Add fuse-io-uring handling into fuse_copy Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 09/17] fuse: {io-uring} Make hash-list req unique finding functions non-static Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 10/17] fuse: Add io-uring sqe commit and fetch support Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 11/17] fuse: {io-uring} Handle teardown of ring entries Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 12/17] fuse: {io-uring} Make fuse_dev_queue_{interrupt,forget} non-static Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 13/17] fuse: Allow to queue fg requests through io-uring Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 14/17] fuse: Allow to queue bg " Bernd Schubert
2025-01-20 1:29 ` [PATCH v10 15/17] fuse: {io-uring} Prevent mount point hang on fuse-server termination Bernd Schubert
2025-01-20 1:29 ` Bernd Schubert [this message]
2025-01-20 1:29 ` [PATCH v10 17/17] fuse: enable fuse-over-io-uring 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=20250120-fuse-uring-for-6-10-rfc4-v10-16-ca7c5d1007c0@ddn.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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