From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "sw.prabhu6@gmail.com" <sw.prabhu6@gmail.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"vincentfu@gmail.com" <vincentfu@gmail.com>,
"joshi.k@samsung.com" <joshi.k@samsung.com>,
Swarna Prabhu <s.prabhu@samsung.com>
Subject: Re: [PATCH blktests v2] nvme/067: test io_uring pass through for NVMe admin queue
Date: Thu, 5 Feb 2026 00:57:36 +0000 [thread overview]
Message-ID: <aYPp3qZTFTmdBRMq@shinmob> (raw)
In-Reply-To: <20260202192631.194256-1-sw.prabhu6@gmail.com>
On Feb 02, 2026 / 11:26, sw.prabhu6@gmail.com wrote:
> From: Swarna Prabhu <s.prabhu@samsung.com>
>
> Simple test to exercise the nvme admin commands usage with
> io uring passthrough interfaces. The motivation for the test
> is to extend the kernel code coverage for NVMe admin commands
> via io_uring passthrough.
>
> Signed-off-by: Swarna Prabhu <s.prabhu@samsung.com>
Thanks for this v2 patch. I applied it. FYI, I took a liberty to fold-in
some edits below:
...
> diff --git a/src/Makefile b/src/Makefile
> index dac07c7..bd94636 100644
> --- a/src/Makefile
> +++ b/src/Makefile
[...]
> + if (cqe)
> + io_uring_cqe_seen(&nvring, cqe);
> + io_uring_queue_exit(&nvring);
> +free_nctrl:
> + free(nctrl);
> +free_fd:
> + close(fd);
I replaced space indent above with a tab.
> +
> + return ret;
> +}
> \ No newline at end of file
> diff --git a/tests/nvme/067 b/tests/nvme/067
> new file mode 100755
> index 0000000..38d55ad
> --- /dev/null
> +++ b/tests/nvme/067
[...]
> +test_device() {
> + echo "Running ${TEST_NAME}"
I added local variable declarations for devname and ctrl_dev here.
> +
> + # extract the ctrl dev from the test dev
> + devname=${TEST_DEV#/dev/}
> + ctrl_dev="/dev/${devname%n*}"
> +
> + # enable io_uring when it is disabled
> + _io_uring_enable
> +
> + if ! sudo src/nvme-passthrough-admin "${ctrl_dev}"; then
> + echo "src/nvme-passthrough-admin failed"
I replaced the program names "src/nvme-passthrough-admin" above with
"src/nvme-passthru-admin-uring".
Thanks again for the contribution!
prev parent reply other threads:[~2026-02-05 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 19:26 [PATCH blktests v2] nvme/067: test io_uring pass through for NVMe admin queue sw.prabhu6
2026-02-05 0:57 ` Shinichiro Kawasaki [this message]
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=aYPp3qZTFTmdBRMq@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=s.prabhu@samsung.com \
--cc=sw.prabhu6@gmail.com \
--cc=vincentfu@gmail.com \
/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