From: Ofir Gal <ofir.gal@volumez.com>
To: shinichiro.kawasaki@wdc.com
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
dwagner@suse.de, chaitanyak@nvidia.com
Subject: [PATCH blktests v2 0/2] md: add regression test for "md/md-bitmap: fix writing non bitmap pages"
Date: Mon, 24 Jun 2024 13:46:16 +0300 [thread overview]
Message-ID: <20240624104620.2156041-1-ofir.gal@volumez.com> (raw)
This patchset adds a regression test for "md/md-bitmap: fix writing non
bitmap pages".
The regression test requires a network layer as the underlying layer of
md, it use nvme-tcp as the network layer.
Changelog:
v2 - applied Shinichiro's comments, use common/nvme instead of
tests/nvme/rc, disconnecting nvme controller on cleanup_nvme_over_tcp
Ofir Gal (2):
nvme: move helper functions to common/nvme
md: add regression test for "md/md-bitmap: fix writing non bitmap
pages"
common/brd | 28 +++
common/nvme | 595 +++++++++++++++++++++++++++++++++++++++++++++++
tests/md/001 | 88 +++++++
tests/md/001.out | 2 +
tests/md/rc | 12 +
tests/nvme/rc | 591 +---------------------------------------------
6 files changed, 726 insertions(+), 590 deletions(-)
create mode 100644 common/brd
create mode 100644 common/nvme
create mode 100755 tests/md/001
create mode 100644 tests/md/001.out
create mode 100644 tests/md/rc
--
2.45.1
next reply other threads:[~2024-06-24 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 10:46 Ofir Gal [this message]
2024-06-24 10:46 ` [PATCH blktests v2 1/2] nvme: move helper functions to common/nvme Ofir Gal
2024-06-26 11:18 ` Shinichiro Kawasaki
2024-07-16 9:23 ` Ofir Gal
2024-07-16 11:10 ` Ofir Gal
2024-06-24 10:46 ` [PATCH blktests v2 2/2] md: add regression test for "md/md-bitmap: fix writing non bitmap pages" Ofir Gal
2024-06-25 15:01 ` Daniel Wagner
2024-07-16 11:49 ` Ofir Gal
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=20240624104620.2156041-1-ofir.gal@volumez.com \
--to=ofir.gal@volumez.com \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox