From: Pavel Begunkov <[email protected]>
To: Dylan Yudaken <[email protected]>, [email protected], [email protected]
Cc: [email protected]
Subject: Re: [PATCH 5.19] io_uring: do not use prio task_work_add in uring_cmd
Date: Thu, 16 Jun 2022 14:53:37 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/16/22 14:50, Dylan Yudaken wrote:
> io_req_task_prio_work_add has a strict assumption that it will only be
> used with io_req_task_complete. There is a codepath that assumes this is
> the case and will not even call the completion function if it is hit.
>
> For uring_cmd with an arbitrary completion function change the call to the
> correct non-priority version.
Reviewed-by: Pavel Begunkov <[email protected]>
> Fixes: ee692a21e9bf8 ("fs,io_uring: add infrastructure for uring-cmd")
> Signed-off-by: Dylan Yudaken <[email protected]>
> ---
> fs/io_uring.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 3aab4182fd89..a7ac2d3bce76 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -5079,7 +5079,7 @@ void io_uring_cmd_complete_in_task(struct io_uring_cmd *ioucmd,
>
> req->uring_cmd.task_work_cb = task_work_cb;
> req->io_task_work.func = io_uring_cmd_work;
> - io_req_task_prio_work_add(req);
> + io_req_task_work_add(req);
> }
> EXPORT_SYMBOL_GPL(io_uring_cmd_complete_in_task);
>
>
> base-commit: b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3
--
Pavel Begunkov
next prev parent reply other threads:[~2022-06-16 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 13:50 [PATCH 5.19] io_uring: do not use prio task_work_add in uring_cmd Dylan Yudaken
2022-06-16 13:53 ` Pavel Begunkov [this message]
2022-06-16 15:14 ` 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] \
/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