From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2 6.6] io_uring/rw: ensure reissue path is correctly handled for IOPOLL
Date: Sat, 9 Aug 2025 20:42:03 -0400 [thread overview]
Message-ID: <1754783337-cf640bd2@stable.kernel.org> (raw)
In-Reply-To: <20250809205420.214099-1-sumanth.gavini@yahoo.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: bcb0fda3c2da9fe4721d3e73d80e778c038e7d27
WARNING: Author mismatch between patch and upstream commit:
Backport author: Sumanth Gavini <sumanth.gavini@yahoo.com>
Commit author: Jens Axboe <axboe@kernel.dk>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Not found
Note: The patch differs from the upstream commit:
---
1: bcb0fda3c2da ! 1: 941165821178 io_uring/rw: ensure reissue path is correctly handled for IOPOLL
@@
## Metadata ##
-Author: Jens Axboe <axboe@kernel.dk>
+Author: Sumanth Gavini <sumanth.gavini@yahoo.com>
## Commit message ##
io_uring/rw: ensure reissue path is correctly handled for IOPOLL
+ commit bcb0fda3c2da9fe4721d3e73d80e778c038e7d27 upstream.
+
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.
@@ Commit message
Reported-by: John Garry <john.g.garry@oracle.com>
Link: https://lore.kernel.org/io-uring/2b43ccfa-644d-4a09-8f8f-39ad71810f41@oracle.com/
Signed-off-by: Jens Axboe <axboe@kernel.dk>
+ Signed-off-by: Sumanth Gavini <sumanth.gavini@yahoo.com>
## io_uring/rw.c ##
@@ io_uring/rw.c: static void io_complete_rw_iopoll(struct kiocb *kiocb, long res)
@@ io_uring/rw.c: static void io_complete_rw_iopoll(struct kiocb *kiocb, long res)
if (unlikely(res != req->cqe.res)) {
- if (res == -EAGAIN && io_rw_should_reissue(req)) {
+ if (res == -EAGAIN && io_rw_should_reissue(req))
- req->flags |= REQ_F_REISSUE | REQ_F_BL_NO_RECYCLE;
+ req->flags |= REQ_F_REISSUE | REQ_F_PARTIAL_IO;
- return;
- }
- req->cqe.res = res;
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-6.6.y | Success | Success |
next prev parent reply other threads:[~2025-08-10 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250809182636.209767-1-sumanth.gavini.ref@yahoo.com>
2025-08-09 18:26 ` [PATCH 6.6] io_uring/rw: ensure reissue path is correctly handled for IOPOLL Sumanth Gavini
2025-08-09 18:38 ` kernel test robot
2025-08-09 20:54 ` [PATCH v2 " Sumanth Gavini
2025-08-10 0:42 ` Sasha Levin [this message]
2025-08-12 10:49 ` Greg KH
2025-08-10 0:42 ` [PATCH " Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1754783337-cf640bd2@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox