From: Jens Axboe <[email protected]>
To: [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 09:14:12 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 16 Jun 2022 06:50:11 -0700, 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.
>
> [...]
Applied, thanks!
[1/1] io_uring: do not use prio task_work_add in uring_cmd
commit: 32fc810b364f3dd30930c594e461ffa1761fef39
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-16 15:14 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
2022-06-16 15:14 ` Jens Axboe [this message]
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=165539245211.4782.5397802277813950857.b4-ty@kernel.dk \
[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