From: Daniel Wagner <wagi@kernel.org>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, Daniel Wagner <wagi@kernel.org>
Subject: [PATCH blktests 2/3] nvme/060: add test nvme fabrics target resetting during I/O
Date: Tue, 18 Mar 2025 11:39:00 +0100 [thread overview]
Message-ID: <20250318-test-target-v1-2-01e01142cf2b@kernel.org> (raw)
In-Reply-To: <20250318-test-target-v1-0-01e01142cf2b@kernel.org>
Newer kernel support to reset the target via the debugfs. Add a new test
case which exercises this interface.
Signed-off-by: Daniel Wagner <wagi@kernel.org>
---
tests/nvme/060 | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/060.out | 2 ++
2 files changed, 90 insertions(+)
diff --git a/tests/nvme/060 b/tests/nvme/060
new file mode 100755
index 0000000000000000000000000000000000000000..16a3c0d20274428ae175693109c694f42004a619
--- /dev/null
+++ b/tests/nvme/060
@@ -0,0 +1,88 @@
+#!/bin/bash
+# SPDX-License-Identifier: GPL-3.0+
+# Copyright (C) 2025 Daniel Wagner, SUSE Labs
+#
+# Test nvme fabrics controller reset/disconnect/reconnect operation during I/O
+# This test is somewhat similar to test 032 but for fabrics controllers.
+
+. tests/nvme/rc
+
+DESCRIPTION="test nvme fabrics target resetting during I/O"
+
+requires() {
+ _nvme_requires
+ _have_loop
+ _have_fio
+ _require_nvme_trtype_is_fabrics
+}
+
+set_conditions() {
+ _set_nvme_trtype "$@"
+}
+
+nvmet_debug_trigger_reset() {
+ local nvmet_subsystem="$1"
+ local dfs_path="${NVMET_DFS}/${nvmet_subsystem}"
+
+ find "${dfs_path}" -maxdepth 1 -type d -name 'ctrl*' -exec sh -c 'echo "fatal" > "$1/state"' _ {} \;
+}
+
+nvmf_wait_for_state() {
+ local def_state_timeout=5
+ local subsys_name="$1"
+ local state="$2"
+ local timeout="${3:-$def_state_timeout}"
+ local nvmedev
+ local state_file
+ local start_time
+ local end_time
+
+ nvmedev=$(_find_nvme_dev "${subsys_name}")
+ state_file="/sys/class/nvme-fabrics/ctl/${nvmedev}/state"
+
+ start_time=$(date +%s)
+ while ! grep -q "${state}" "${state_file}"; do
+ sleep 1
+ end_time=$(date +%s)
+ if (( end_time - start_time > timeout )); then
+ echo "expected state \"${state}\" not " \
+ "reached within ${timeout} seconds"
+ return 1
+ fi
+ done
+
+ return 0
+}
+
+nvmet_reset_loop() {
+ while true; do
+ nvmet_debug_trigger_reset "${def_subsysnqn}"
+ sleep 2
+ done
+}
+
+test() {
+ echo "Running ${TEST_NAME}"
+
+ _setup_nvmet
+
+ _nvmet_target_setup
+
+ nvmet_reset_loop &
+ fio_pid=$!
+
+ # Try to trigger resets when the host is in different states connected,
+ # or connecting by calling target reset with an even number and the
+ # reconnect attempt with an uneven timeout.
+ for ((i = 0; i <= 5; i++)); do
+ _nvme_connect_subsys --keep-alive-tmo 1 --reconnect-delay 1
+ sleep 3
+ _nvme_disconnect_subsys >> "$FULL" 2>&1
+ done
+
+ { kill "${fio_pid}"; wait; } &> /dev/null
+
+ _nvmet_target_cleanup
+
+ echo "Test complete"
+}
diff --git a/tests/nvme/060.out b/tests/nvme/060.out
new file mode 100644
index 0000000000000000000000000000000000000000..517ff2dfcfd41c4088991e669af9fef52bde570b
--- /dev/null
+++ b/tests/nvme/060.out
@@ -0,0 +1,2 @@
+Running nvme/060
+Test complete
--
2.48.1
next prev parent reply other threads:[~2025-03-18 10:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:38 [PATCH blktests 0/3] blktests: add target test cases Daniel Wagner
2025-03-18 10:38 ` [PATCH blktests 1/3] common/nvme: add debug nvmet path variable Daniel Wagner
2025-03-18 20:37 ` Chaitanya Kulkarni
2025-04-04 8:03 ` Shinichiro Kawasaki
2025-04-04 10:08 ` Daniel Wagner
2025-03-18 10:39 ` Daniel Wagner [this message]
2025-03-18 20:40 ` [PATCH blktests 2/3] nvme/060: add test nvme fabrics target resetting during I/O Chaitanya Kulkarni
2025-03-19 9:26 ` Daniel Wagner
2025-03-19 16:54 ` Chaitanya Kulkarni
2025-04-04 8:08 ` Shinichiro Kawasaki
2025-04-04 10:15 ` Daniel Wagner
2025-03-18 10:39 ` [PATCH blktests 3/3] nvme/061: add test teardown and setup fabrics target " Daniel Wagner
2025-03-18 20:42 ` Chaitanya Kulkarni
2025-04-04 8:22 ` Shinichiro Kawasaki
2025-04-04 10:16 ` 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=20250318-test-target-v1-2-01e01142cf2b@kernel.org \
--to=wagi@kernel.org \
--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.