From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, Dylan Yudaken <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH] io_uring: always prep_async for drain requests
Date: Fri, 27 Jan 2023 06:46:02 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 27 Jan 2023 02:59:11 -0800, Dylan Yudaken wrote:
> Drain requests all go through io_drain_req, which has a quick exit in case
> there is nothing pending (ie the drain is not useful). In that case it can
> run the issue the request immediately.
>
> However for safety it queues it through task work.
> The problem is that in this case the request is run asynchronously, but
> the async work has not been prepared through io_req_prep_async.
>
> [...]
Applied, thanks!
[1/1] io_uring: always prep_async for drain requests
commit: ef5c600adb1d985513d2b612cc90403a148ff287
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-01-27 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 10:59 [PATCH] io_uring: always prep_async for drain requests Dylan Yudaken
2023-01-27 13:46 ` 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=167482716231.273660.4883362917562226118.b4-ty@kernel.dk \
[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