io_uring/rw: ensure retry condition isn't lost
authorJens Axboe <axboe@kernel.dk>
Wed, 17 Apr 2024 15:23:55 +0000 (09:23 -0600)
committerJens Axboe <axboe@kernel.dk>
Wed, 17 Apr 2024 15:23:55 +0000 (09:23 -0600)
commitdf604d2ad480fcf7b39767280c9093e13b1de952
tree10fa5144873d57d4cfd6f56af02e40e3585b31f6
parent24c3fc5c75c5b9d471783b4a4958748243828613
io_uring/rw: ensure retry condition isn't lost

A previous commit removed the checking on whether or not it was possible
to retry a request, since it's now possible to retry any of them. This
would previously have caused the request to have been ended with an error,
but now the retry condition can simply get lost instead.

Cleanup the retry handling and always just punt it to task_work, which
will queue it with io-wq appropriately.

Reported-by: Changhui Zhong <czhong@redhat.com>
Tested-by: Ming Lei <ming.lei@redhat.com>
Fixes: cca6571381a0 ("io_uring/rw: cleanup retry path")
Signed-off-by: Jens Axboe <axboe@kernel.dk>
io_uring/io_uring.c
io_uring/io_uring.h
io_uring/rw.c