From: Jesse Taube <jtaubepe@redhat.com>
To: linux-block@vger.kernel.org
Cc: linux-nvme@lists.infradead.org, shinichiro.kawasaki@wdc.com,
John Meneghini <jmeneghi@redhat.com>,
Daniel Wagner <dwagner@suse.de>,
Jesse Taube <jtaubepe@redhat.com>
Subject: [blktests v3 0/2] Test multipath and marginal ports
Date: Fri, 28 Aug 2026 11:30:27 -0400 [thread overview]
Message-ID: <20260828153029.853768-1-jtaubepe@redhat.com> (raw)
Tests for the upcoming nvme-fc: FPIN link integrity handling set.
It tests for various multipath and marginal port
scenarios, while confirming the port usage and state. The test is
intended to emulate receiving an FPIN event in a multipath environment.
In V3 various generic link checking code was move to common/nvme.
This is so that it can be used by other tests to check if multipath
working correctly, even on kernels that dont support marginal paths.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=220329
Link: https://github.com/linux-blktests/blktests/pull/264
V1 -> V2:
- Fix timeout issue
- Skip test if /sys/class/fcloop/ctl/set_marginal_rport does not exist
- Wrap lines at 80col
- Add John's tags
- Fix various change requests from mailing list
V2 -> V3:
- Add tests for inaccessable paths
- Fix fio not exiting
- Move generic code to common/nvme
Jesse Taube (2):
nvme: Add _setup_nvmet_port_marginal
nvme/070: Test multipath and marginal ports
common/nvme | 278 +++++++++++++++++++++++++++
tests/nvme/070 | 454 +++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/070.out | 49 +++++
3 files changed, 781 insertions(+)
create mode 100755 tests/nvme/070
create mode 100644 tests/nvme/070.out
--
2.54.0
next reply other threads:[~2026-08-28 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 15:30 Jesse Taube [this message]
2026-08-28 15:30 ` [blktests v3 1/2] nvme: Add _setup_nvmet_port_marginal Jesse Taube
2026-08-28 15:30 ` [blktests v3 2/2] nvme/070: Test multipath and marginal ports Jesse Taube
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=20260828153029.853768-1-jtaubepe@redhat.com \
--to=jtaubepe@redhat.com \
--cc=dwagner@suse.de \
--cc=jmeneghi@redhat.com \
--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