Hi Kevin, On Mon, Oct 13, 2025 at 08:07:51PM +0300, Kevin Lumik wrote: > Hello, > > I've identified the first bad commit using git bisect: > > 90bfb28d5fa8127a113a140c9791ea0b40ab156a is the first bad commit > commit 90bfb28d5fa8127a113a140c9791ea0b40ab156a > Author: Jens Axboe <[email protected]> > Date: Tue Sep 10 08:57:04 2024 -0600 > > io_uring/rw: drop -EOPNOTSUPP check in __io_complete_rw_common() > > A recent change ensured that the necessary -EOPNOTSUPP -> -EAGAIN > transformation happens inline on both the reader and writer side, > and hence there's no need to check for both of these anymore on > the completion handler side. > > Signed-off-by: Jens Axboe <[email protected]> > > io_uring/rw.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-)
Great news, thank you for doing this work. I just have forwarded the information to the io-uring maintainer, let's see if that rings a bell. Regards, Salvatore
