From: Andrea Parri <parri.andrea@gmail.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org
Cc: Andrea Parri <parri.andrea@gmail.com>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
Daniel Wagner <dwagner@suse.de>,
linux-nvme@lists.infradead.org
Subject: [PATCH blktests 0/4] nvme: add nvmet zone report and FC regression tests
Date: Wed, 14 Oct 2026 19:00:37 +0200 [thread overview]
Message-ID: <20261014170046.2516-1-parri.andrea@gmail.com> (raw)
Add regression tests for three nvmet bugs fixed by the kernel series
"nvmet: fix stale data exposure and ZNS validation" [1]:
nvme/071 "nvmet-fc: only send read data for successful commands"
nvme/072 "nvmet: zns: don't leak stale memory in zone management receive"
nvme/073 "nvmet: zns: reject a NUMD whose byte count wraps"
The nvme/072 fix is already applied to nvme-7.4; the other two are still
under review.
Patch 1 adds the zoned null_blk target setup, cleanup and zone report
status check that nvme/072 and nvme/073 share. Patches 2-4 add one test
each, with a small C helper for nvme/071 and nvme/072 where nvme-cli
cannot express the check.
All three tests run on every configured transport. On a kernel without
the fixes, nvme/072 and nvme/073 fail over loop, tcp, rdma and fc, and
nvme/071 fails over fc, the only affected transport. All three pass
with the fixes applied.
The tests take the next free numbers, nvme/071 to nvme/073. If other
nvme tests land first, I'm happy to renumber them and resend.
[1] https://lore.kernel.org/r/20261012141239.156408-1-parri.andrea@gmail.com
Andrea Parri (4):
nvme/rc: add zoned null_blk target helpers
nvme/071: test that nvmet sends no data for a failed read
nvme/072: test nvmet zone report initialization and length
nvme/073: test that nvmet rejects a zone report NUMD that wraps
src/.gitignore | 2 +
src/Makefile | 2 +
src/nvme-sentinel-read.c | 89 +++++++++++++++++++++
src/nvme-zone-report.c | 165 +++++++++++++++++++++++++++++++++++++++
tests/nvme/071 | 80 +++++++++++++++++++
tests/nvme/071.out | 2 +
tests/nvme/072 | 68 ++++++++++++++++
tests/nvme/072.out | 2 +
tests/nvme/073 | 46 +++++++++++
tests/nvme/073.out | 2 +
tests/nvme/rc | 61 +++++++++++++++
11 files changed, 519 insertions(+)
create mode 100644 src/nvme-sentinel-read.c
create mode 100644 src/nvme-zone-report.c
create mode 100755 tests/nvme/071
create mode 100644 tests/nvme/071.out
create mode 100755 tests/nvme/072
create mode 100644 tests/nvme/072.out
create mode 100755 tests/nvme/073
create mode 100644 tests/nvme/073.out
--
2.53.0
next reply other threads:[~2026-10-14 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 17:00 Andrea Parri [this message]
2026-10-14 17:00 ` [PATCH blktests 1/4] nvme/rc: add zoned null_blk target helpers Andrea Parri
2026-10-14 17:00 ` [PATCH blktests 2/4] nvme/071: test that nvmet sends no data for a failed read Andrea Parri
2026-10-14 17:00 ` [PATCH blktests 3/4] nvme/072: test nvmet zone report initialization and length Andrea Parri
2026-10-14 17:00 ` [PATCH blktests 4/4] nvme/073: test that nvmet rejects a zone report NUMD that wraps Andrea Parri
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=20261014170046.2516-1-parri.andrea@gmail.com \
--to=parri.andrea@gmail.com \
--cc=dwagner@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox