On Fri, 27 Jan 2023 05:52:23 -0800, Dylan Yudaken wrote:
> Many ops such as statx do not support nonblock issuing (for now). At the
> moment the code goes through the issue call just to receive -EAGAIN and
> then be run async. There is no need for this as internally the
> REQ_F_FORCE_ASYNC flag can just be added on.
>
> The upside for this is generally minimal, and possibly you may decide that
> it's not worth the extra risk of bugs. Though as far as I can tell the
> risk is simply doing a blocking call from io_uring_enter(2), which while
> still a bug is not disasterous.
>
> [...]
Applied, thanks!
[1/4] io_uring: if a linked request has REQ_F_FORCE_ASYNC then run it async
(no commit info)
[2/4] io_uring: for requests that require async, force it
(no commit info)
[3/4] io_uring: always go async for unsupported fadvise flags
(no commit info)
[4/4] io_uring: always go async for unsupported open flags
(no commit info)
Best regards,
--
Jens Axboe
