All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <keith.busch@wdc.com>,
	Omar Sandoval <osandov@fb.com>,
	linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 2/9] nvme/rc: clear allowed_hosts subdirectory
Date: Mon, 22 Nov 2021 08:55:17 +0100	[thread overview]
Message-ID: <20211122075524.26207-3-hare@suse.de> (raw)
In-Reply-To: <20211122075524.26207-1-hare@suse.de>

When removing a subsystem we need to clear out the allowed_hosts
subdirectory, otherwise removal will fail.

Signed-off-by: Hannes Reinecke <hare@suse.de>
---
 tests/nvme/rc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/nvme/rc b/tests/nvme/rc
index 086c094..aa223df 100644
--- a/tests/nvme/rc
+++ b/tests/nvme/rc
@@ -262,6 +262,7 @@ _remove_nvmet_subsystem() {
 	local subsys_path="${NVMET_CFS}/subsystems/${nvmet_subsystem}"
 
 	_remove_nvmet_ns "${nvmet_subsystem}" "1"
+	rm "${subsys_path}"/allowed_hosts/*
 	rmdir "${subsys_path}"
 }
 
-- 
2.26.2



  parent reply	other threads:[~2021-11-22  8:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22  7:55 [PATCHv2 blktests 0/9] Testsuite for nvme in-band authentication Hannes Reinecke
2021-11-22  7:55 ` [PATCH 1/9] nvme/rc: do not print error message when no nvme device is found Hannes Reinecke
2021-11-22  8:49   ` Sagi Grimberg
2021-11-22  7:55 ` Hannes Reinecke [this message]
2021-11-22  8:49   ` [PATCH 2/9] nvme/rc: clear allowed_hosts subdirectory Sagi Grimberg
2021-11-22  7:55 ` [PATCH 3/9] nvme/rc: add functions for in-band authentication Hannes Reinecke
2021-11-22  8:52   ` Sagi Grimberg
2021-11-22  9:24     ` Hannes Reinecke
2021-11-22  7:55 ` [PATCH 4/9] nvme/039: simple test for nvmeof-tcp connection Hannes Reinecke
2021-11-22  8:52   ` Sagi Grimberg
2021-11-22  9:18     ` Hannes Reinecke
2021-11-22  9:40       ` Sagi Grimberg
2021-11-22  9:41         ` Hannes Reinecke
2021-11-22  7:55 ` [PATCH 5/9] nvme/040: create an authenticated " Hannes Reinecke
2021-11-22  8:57   ` Sagi Grimberg
2021-11-22  9:22     ` Hannes Reinecke
2021-11-22  9:44       ` Sagi Grimberg
2021-11-22  7:55 ` [PATCH 6/9] nvme/041: test different key types Hannes Reinecke
2021-11-22  8:58   ` Sagi Grimberg
2021-11-22  9:25     ` Hannes Reinecke
2021-11-22  9:45       ` Sagi Grimberg
2021-11-22  7:55 ` [PATCH 7/9] nvme/042: test hash and dhgroup variations Hannes Reinecke
2021-11-22  7:55 ` [PATCH 8/9] nvme/043: test bi-directional authentication Hannes Reinecke
2021-11-22  7:55 ` [PATCH 9/9] nvme/044: test re-authentication Hannes Reinecke
2021-11-22  9:02   ` Sagi Grimberg
2021-11-22  9:40     ` Hannes Reinecke

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=20211122075524.26207-3-hare@suse.de \
    --to=hare@suse.de \
    --cc=hch@lst.de \
    --cc=keith.busch@wdc.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=osandov@fb.com \
    --cc=sagi@grimberg.me \
    /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.