[PATCHv2 blktests 2/2] nvme: add test for writing to file-ns just after disabling it
Nilay Shroff
nilay at linux.ibm.com
Wed Dec 4 03:47:48 PST 2024
This is a regression test for commit 505363957fad ("nvmet: fix nvme
status code when namespace is disabled")[1].
This test creates a regular file backed loop target namespace, disables
the asynchronous event notification for ns-changed events and then write
to the namespace just after disabling it.
[1] https://lore.kernel.org/linux-nvme/tqcy3sveity7p56v7ywp7ssyviwcb3w4623cnxj3knoobfcanq@yxgt2mjkbkam/
Signed-off-by: Nilay Shroff <nilay at linux.ibm.com>
---
tests/nvme/055 | 117 +++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/055.out | 2 +
2 files changed, 119 insertions(+)
create mode 100755 tests/nvme/055
create mode 100644 tests/nvme/055.out
diff --git a/tests/nvme/055 b/tests/nvme/055
new file mode 100755
index 0000000..f1f19fe
--- /dev/null
+++ b/tests/nvme/055
@@ -0,0 +1,117 @@
+#!/bin/bash
+# SPDX-License-Identifier: GPL-3.0+
+# Copyright (C) 2024 Nilay Shroff
+#
+# Regression test for commit 505363957fad ("nvmet: fix nvme
+# status code when namespace is disabled").
+
+. tests/nvme/rc
+
+DESCRIPTION="Test nvme write to a loop target ns just after ns is disabled"
+
+QUICK=1
+
+requires() {
+ _nvme_requires
+ _have_loop
+ _require_nvme_trtype_is_loop
+ _have_kernel_option DEBUG_ATOMIC_SLEEP
+}
+
+set_conditions() {
+ _set_nvme_trtype "$@"
+}
+
+nvmf_disable_ns_change_aen() {
+
+ local disk="$1"
+ local timeout="5"
+
+ # get async event configuration value
+ aen_conf=$(nvme get-feature "$disk" --feature-id=0xB | cut -d':' -f3)
+
+ # disable async ns change event notfication
+ disable_ns_change=$(( aen_conf & 0xFEFF ))
+
+ # stop receiving aen event for ns change from target
+ nvme set-feature "$disk" --feature-id=0xB \
+ --value="$disable_ns_change" 2>>"$FULL" 1>&2
+
+ start_time=$(date +%s)
+
+ while true; do
+ aen_conf=$(nvme get-feature "$disk" \
+ --feature-id=0xB | cut -d':' -f3)
+
+ # Validate whether ns-changed notification is disabled or not;
+ # If it's already disabled then break and return success
+ if ! (( aen_conf & 0x100 )); then
+ break
+ fi
+
+ sleep 1
+
+ end_time=$(date +%s)
+
+ if (( end_time - start_time > timeout )); then
+ echo "can't disable ns-changed async event "\
+ "notification within $timeout seconds"
+ return 1
+ fi
+ done
+
+ return 0
+}
+
+test() {
+ echo "Running ${TEST_NAME}"
+
+ local iteration=1 i=0
+
+ _setup_nvmet
+
+ _nvmet_target_setup
+
+ _nvme_connect_subsys
+
+ img="$(mktemp /tmp/blk_img_XXXXXX)"
+ dd if=/dev/urandom of="$img" bs=512 count=1 status=none
+
+ subsys_path="${NVMET_CFS}/subsystems/${def_subsysnqn}"
+ ns_path="${subsys_path}/namespaces/${def_nsid}"
+
+ while (( i < iteration )); do
+ # Wait until async request is processed and default ns
+ # is created
+ if ! _nvmf_wait_for_ns "${def_subsys_uuid}" created; then
+ echo "FAIL"
+ break
+ fi
+
+ disk="/dev/$(_find_nvme_ns "${def_subsys_uuid}")"
+
+ # Disable ns change async event notification from target. It
+ # would ensure that when we disable the target ns, the host
+ # would not receive ns removal notification from target and
+ # so from host we can attempt writing to a disabled ns.
+ if ! nvmf_disable_ns_change_aen "${disk}"; then
+ echo "FAIL"
+ break
+ fi
+
+ # disable target namespace and write to it
+ echo 0 > ${ns_path}/enable
+ nvme write --start-block=1 --block-count=0 \
+ --data-size=512 --data="$img" "$disk" 2>>"$FULL"
+
+ ((i++))
+ done
+
+ rm "$img"
+
+ _nvme_disconnect_subsys >> "$FULL" 2>&1
+
+ _nvmet_target_cleanup
+
+ echo "Test complete"
+}
diff --git a/tests/nvme/055.out b/tests/nvme/055.out
new file mode 100644
index 0000000..bbefc28
--- /dev/null
+++ b/tests/nvme/055.out
@@ -0,0 +1,2 @@
+Running nvme/055
+Test complete
--
2.45.2
More information about the Linux-nvme
mailing list