From: Daniel Wagner <dwagner@suse.de>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Daniel Wagner <wagi@kernel.org>
Subject: [PATCH blktests 1/5] common/nvme: don't truncate the full log when disconnecting
Date: Wed, 14 Oct 2026 09:51:47 +0200 [thread overview]
Message-ID: <20261014-nvme-isolcpu-v1-1-2fd175a8ef00@kernel.org> (raw)
In-Reply-To: <20261014-nvme-isolcpu-v1-0-2fd175a8ef00@kernel.org>
From: Daniel Wagner <wagi@kernel.org>
_nvme_disconnect_ctrl and _nvme_disconnect_subsys redirect the output
of nvme disconnect with '&>' into $FULL. This truncates the file and
everything a test logged before the disconnect is lost, e.g. the fio
command lines logged by _run_fio.
Append to $FULL instead.
Signed-off-by: Daniel Wagner <wagi@kernel.org>
---
common/nvme | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/common/nvme b/common/nvme
index 8c907c34910d..1b3090e0a5da 100644
--- a/common/nvme
+++ b/common/nvme
@@ -290,7 +290,7 @@ _nvme_disconnect_ctrl() {
if [[ -d "${ctrl_dir}" ]]; then
local ret
- nvme disconnect --device "${ctrl}" &> "${FULL}"
+ nvme disconnect --device "${ctrl}" &>> "${FULL}"
ret=$?
if [[ ${ret} -ne 0 ]]; then
echo "FAIL: nvme disconnect returned error code: ${ret}"
@@ -574,7 +574,7 @@ _nvme_disconnect_subsys() {
esac
done
- nvme disconnect --nqn "${subsysnqn}" &> "${FULL}"
+ nvme disconnect --nqn "${subsysnqn}" &>> "${FULL}"
ret=$?
if [[ ${ret} -ne 0 ]]; then
echo "FAIL: nvme disconnect returned error code: ${ret}"
--
2.56.0
next prev parent reply other threads:[~2026-10-14 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 7:51 [PATCH blktests 0/5] nvme: tests for isolated CPUs and fabrics queue mapping Daniel Wagner
2026-10-14 7:51 ` Daniel Wagner [this message]
2026-10-14 7:51 ` [PATCH blktests 2/5] nvme/070: test connect with an isolated CPU Daniel Wagner
2026-10-14 7:51 ` [PATCH blktests 3/5] nvme/071: test I/O queue limits per queue type Daniel Wagner
2026-10-14 7:51 ` [PATCH blktests 4/5] nvme/072: test poll support without poll queues Daniel Wagner
2026-10-14 7:51 ` [PATCH blktests 5/5] nvme/073: test reconnect with fewer I/O queues 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=20261014-nvme-isolcpu-v1-1-2fd175a8ef00@kernel.org \
--to=dwagner@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=wagi@kernel.org \
/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