From: Daniel Wagner <dwagner@suse.de>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Daniel Wagner <dwagner@suse.de>
Subject: [PATCH blktests v2 0/2] make nvme/048 checks more robust
Date: Mon, 4 Mar 2024 14:48:24 +0100 [thread overview]
Message-ID: <20240304134826.31965-1-dwagner@suse.de> (raw)
The nvme/048 tests fails with the fc transport because the check logic is racing
with the reset code in the target. By making the checks a bit more robust in
blktests, this test passes for all transports.
changes
v2:
- added RB tags
- refactored exit path as suggested by Shinichiro
v1:
- initial version
- https://lore.kernel.org/linux-nvme/20240301094817.29491-1-dwagner@suse.de/
*** BLURB HERE ***
Daniel Wagner (2):
nvme/048: remove unused argument for set_qid_max
nvme/048: make queue count check retry-able
tests/nvme/048 | 27 ++++++++++++++++++++-------
1 file changed, 20 insertions(+), 7 deletions(-)
--
2.44.0
next reply other threads:[~2024-03-04 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:48 Daniel Wagner [this message]
2024-03-04 13:48 ` [PATCH blktests v2 1/2] nvme/048: remove unused argument for set_qid_max Daniel Wagner
2024-03-04 13:48 ` [PATCH blktests v2 2/2] nvme/048: make queue count check retry-able Daniel Wagner
2024-03-05 1:29 ` [PATCH blktests v2 0/2] make nvme/048 checks more robust Shinichiro Kawasaki
2024-03-05 7:20 ` Daniel Wagner
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=20240304134826.31965-1-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=chaitanyak@nvidia.com \
--cc=kbusch@kernel.org \
--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