MIRRORS/linux-yocto
1
0
Fork 0
mirror of git://git.yoctoproject.org/linux-yocto.git synced 2025-10-22 23:13:01 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

io_uring/rw: don't gate retry on completion context

Browse Source 
nvme multipath reports that they see spurious -EAGAIN bubbling back to
userspace, which is caused by how they handle retries internally through
a kworker. However, any data that needs preserving or importing for
a read/write request has always been done so at prep time, and we can
sanely skip this check.

Reported-by: "Haeuptle, Michael" <michael.haeuptle@hpe.com>
Link: https://lore.kernel.org/io-uring/DS7PR84MB31105C2C63CFA47BE8CBD6EE95102@DS7PR84MB3110.NAMPRD84.PROD.OUTLOOK.COM/
Signed-off-by: Jens Axboe <axboe@kernel.dk>
This commit is contained in:
Jens Axboe 2025-01-07 11:07:47 -07:00
parent d803d12394
commit b08e020450
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
io_uring/rw.c
View File

@ -475,12 +475,6 @@ static bool io_rw_should_reissue(struct io_kiocb *req)
*/ */
if (percpu_ref_is_dying(&ctx->refs)) if (percpu_ref_is_dying(&ctx->refs))
return false; return false;
/*
* Play it safe and assume not safe to re-import and reissue if we're
* not in the original thread group (or in task context).
*/
if (!same_thread_group(req->tctx->task, current) || !in_task())
return false;
io_meta_restore(io, &rw->kiocb); io_meta_restore(io, &rw->kiocb);
iov_iter_restore(&io->iter, &io->iter_state); iov_iter_restore(&io->iter, &io->iter_state);