From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Keith Busch <kbusch@meta.com>
Cc: Keith Busch <kbusch@kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>,
"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH blktests] io_uring user metadata offset test
Date: Sat, 8 Nov 2025 02:09:33 +0000 [thread overview]
Message-ID: <5d630378-6653-4b2b-b3ec-946bf2671849@nvidia.com> (raw)
In-Reply-To: <20251107231836.1280881-1-kbusch@meta.com>
On 11/7/25 15:18, Keith Busch wrote:
> diff --git a/tests/block/043 b/tests/block/043
> new file mode 100755
> index 0000000..0e6a6cb
> --- /dev/null
> +++ b/tests/block/043
> @@ -0,0 +1,27 @@
> +#!/bin/bash
> +
> +. tests/block/rc
> +
> +DESCRIPTION="Test userspace metadataoffsets"
nit:- DESCRIPTION="Test userspace metadata offsets" ? OR
"verify io_uring PI metadata integrity across buffer offsets" ?
> +QUICK=1
> +
> +device_requires() {
> + _test_dev_has_metadata
> + _test_dev_disables_extended_lba
> +}
> +
> +requires() {
> + _have_kernel_option IO_URING
this requires a specific kernel version or higher for
IO_URING to have this metadata support ? OR any version
of kernel would work ?
> + _have_kernel_option BLK_DEV_INTEGRITY
looking at blktests, we need something like :-
diff --git a/common/rc b/common/rc
index 86bb991..545da61 100644
--- a/common/rc
+++ b/common/rc
@@ -226,6 +226,12 @@ _have_kernel_option() {
return 0
}
+_have_kernel_options() {
+ for opt in "$@"; do
+ _have_kernel_option "$opt" || return 1
+ done
+}
+
# Compare the version string in $1 in "a.b.c" format with "$2.$3.$4".
# If "a.b.c" is smaller than "$2.$3.$4", return true. Otherwise, return
# false.
not asking you to do anything, I'll send a patch and remove these
duplicates.
> +}
> +
> +test_device() {
> + echo "Running ${TEST_NAME}"
> +
> + if ! src/metadata ${TEST_DEV}; then
> + echo "src/dio-offsets failed"
nit:- echo "src/metadata failed" ?
> + fi
> +
> + echo "Test complete"
> +}
> +
> diff --git a/tests/block/043.out b/tests/block/043.out
> new file mode 100644
> index 0000000..fda7fca
> --- /dev/null
> +++ b/tests/block/043.out
> @@ -0,0 +1,2 @@
> +Running block/043
-ck
next prev parent reply other threads:[~2025-11-08 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 23:18 [PATCH blktests] io_uring user metadata offset test Keith Busch
2025-11-08 2:09 ` Chaitanya Kulkarni [this message]
2025-11-19 16:50 ` Keith Busch
2025-11-08 3:26 ` Chaitanya Kulkarni
2025-11-11 7:58 ` Shinichiro Kawasaki
2025-11-19 16:10 ` Keith Busch
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=5d630378-6653-4b2b-b3ec-946bf2671849@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.