From: luhongfei <[email protected]>
To: Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>,
[email protected] (open list:IO_URING),
[email protected] (open list)
Cc: [email protected], luhongfei <[email protected]>
Subject: [PATCH] Subject: io_uring: Fix bug in io_fallback_req_func that can cause deadlock
Date: Fri, 12 May 2023 17:56:55 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
There was a bug in io_fallback_req_func that can cause deadlocks
because uring_lock was not released when return.
This patch releases the uring_lock before return.
Signed-off-by: luhongfei <[email protected]>
---
io_uring/io_uring.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
mode change 100644 => 100755 io_uring/io_uring.c
diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index 3bca7a79efda..1af793c7b3da
--- a/io_uring/io_uring.c
+++ b/io_uring/io_uring.c
@@ -252,8 +252,10 @@ static __cold void io_fallback_req_func(struct work_struct *work)
mutex_lock(&ctx->uring_lock);
llist_for_each_entry_safe(req, tmp, node, io_task_work.node)
req->io_task_work.func(req, &ts);
- if (WARN_ON_ONCE(!ts.locked))
+ if (WARN_ON_ONCE(!ts.locked)) {
+ mutex_unlock(&ctx->uring_lock);
return;
+ }
io_submit_flush_completions(ctx);
mutex_unlock(&ctx->uring_lock);
}
--
2.39.0
next reply other threads:[~2023-05-12 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 9:56 luhongfei [this message]
2023-05-12 13:58 ` [PATCH] Subject: io_uring: Fix bug in io_fallback_req_func that can cause deadlock Jens Axboe
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 \
[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