From: Anuj Gupta <anuj20.g@samsung.com>
To: axboe@kernel.dk, kbusch@kernel.org
Cc: io-uring@vger.kernel.org, joshi.k@samsung.com,
Anuj Gupta <anuj20.g@samsung.com>
Subject: [PATCH] io_uring/rw: handle IORING_OP_URING_CMD128 in iopoll dispatch
Date: Thu, 19 Feb 2026 18:01:36 +0530 [thread overview]
Message-ID: <20260219123136.155590-1-anuj20.g@samsung.com> (raw)
In-Reply-To: CGME20260219123601epcas5p3102acea27f92bc92a8e482c18e74103f@epcas5p3.samsung.com
io_uring_classic_poll() special-cases only IORING_OP_URING_CMD for
uring-cmd iopoll dispatch. IORING_OP_URING_CMD128 falls into the generic
rw branch, which calls file->f_op->iopoll() after casting to struct io_rw.
That is the wrong callback path for uring_cmd requests, which should go
through ->uring_cmd_iopoll(). Treat IORING_OP_URING_CMD128 the same as
IORING_OP_URING_CMD in io_uring_classic_poll().
Fixes: 1cba30bf9fdd ("io_uring: add support for IORING_SETUP_SQE_MIXED")
Signed-off-by: Anuj Gupta <anuj20.g@samsung.com>
---
io_uring/rw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/io_uring/rw.c b/io_uring/rw.c
index b3971171c342..0eede0c09eaf 100644
--- a/io_uring/rw.c
+++ b/io_uring/rw.c
@@ -1254,7 +1254,7 @@ static int io_uring_classic_poll(struct io_kiocb *req, struct io_comp_batch *iob
{
struct file *file = req->file;
- if (req->opcode == IORING_OP_URING_CMD) {
+ if (req->opcode == IORING_OP_URING_CMD || req->opcode == IORING_OP_URING_CMD128) {
struct io_uring_cmd *ioucmd;
ioucmd = io_kiocb_to_cmd(req, struct io_uring_cmd);
--
2.25.1
next parent reply other threads:[~2026-02-19 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260219123601epcas5p3102acea27f92bc92a8e482c18e74103f@epcas5p3.samsung.com>
2026-02-19 12:31 ` Anuj Gupta [this message]
2026-02-19 13:32 ` [PATCH] io_uring/rw: handle IORING_OP_URING_CMD128 in iopoll dispatch Kanchan Joshi
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=20260219123136.155590-1-anuj20.g@samsung.com \
--to=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=kbusch@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