On 05/03/2025 21:06, Jens Axboe wrote:
The IOPOLL path posts CQEs when the io_kiocb is marked as completed,
so it cannot rely on the usual retry that non-IOPOLL requests do for
read/write requests.
If -EAGAIN is received and the request should be retried, go through
the normal completion path and let the normal flush logic catch it and
reissue it, like what is done for !IOPOLL reads or writes.
Fixes: d803d123948f ("io_uring/rw: handle -EAGAIN retry at IO completion time")
Reported-by: John Garry<john.g.garry@xxxxxxxxxx>
Link:https://urldefense.com/v3/__https://lore.kernel.org/io-
uring/2b43ccfa-644d-4a09-8f8f-39ad71810f41@xxxxxxxxxx/__;!!
ACWV5N9M2RV99hQ!J4rCZomS7jntxigOWFGkQC3hFMb5EZf3-aZG4hZCB6n_quTKHse9g-
WSxf46gMXpEfyzjaAQKTff2J9o0pg$
Signed-off-by: Jens Axboe<axboe@xxxxxxxxx>
This solves the issue which I was seeing, so:
Tested-by: John Garry <john.g.garry@xxxxxxxxxx>
cheers
