From: Govindarajulu Varadarajan <govind.varadar@gmail.com>
To: io-uring@vger.kernel.org, axboe@kernel.dk
Cc: ming.lei@redhat.com, kbusch@kernel.org, hch@lst.de,
sagi@grimberg.me, miklos@szeredi.hu,
Govindarajulu Varadarajan <govind.varadar@gmail.com>
Subject: [PATCH 0/2] io_uring: Add macro to validate SQE cmd size
Date: Thu, 29 Jan 2026 12:13:45 -0800 [thread overview]
Message-ID: <20260129201347.411015-1-govind.varadar@gmail.com> (raw)
This patch series introduces macros IO_URING_SQE_CMD() and
IO_URING_SQE128_CMD() for accessing cmd struct from io_uring SQEs,
providing compile-time type checking and size validation. The series
also updates ublk driver to check the SQE128 flag before accessing the
cmd structure.
Testing:
- Compile test only. (trivial changes)
- Validated IO_URING_SQE_CMD() and IO_URING_SQE128_CMD() with struct
size < 16, = 16, > 16 for IO_URING_SQE_CMD() and < 80, = 80, > 80 for
IO_URING_SQE128_CMD().
Govindarajulu Varadarajan (2):
io_uring: Add size check for sqe->cmd
block/ublk_drv: Validate SQE128 flag before accessing the cmd
drivers/block/ublk_drv.c | 20 +++++++++++---------
drivers/nvme/host/ioctl.c | 2 +-
fs/fuse/dev_uring.c | 6 ++++--
include/linux/io_uring/cmd.h | 15 +++++++++++----
4 files changed, 27 insertions(+), 16 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-29 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 20:13 Govindarajulu Varadarajan [this message]
2026-01-29 20:13 ` [PATCH 1/2] io_uring: Add size check for sqe->cmd Govindarajulu Varadarajan
2026-01-29 20:19 ` Jens Axboe
2026-01-29 20:48 ` Caleb Sander Mateos
2026-01-30 5:11 ` Christoph Hellwig
2026-01-29 20:13 ` [PATCH 2/2] block/ublk_drv: Validate SQE128 flag before accessing the cmd Govindarajulu Varadarajan
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=20260129201347.411015-1-govind.varadar@gmail.com \
--to=govind.varadar@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=miklos@szeredi.hu \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
/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