From: Daniel Wagner <wagi@kernel.org>
To: James Smart <james.smart@broadcom.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Cc: Hannes Reinecke <hare@suse.de>, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Daniel Wagner <wagi@kernel.org>
Subject: [PATCH v4 10/14] nvmet-fcloop: don't wait for lport cleanup
Date: Thu, 10 Apr 2025 13:41:13 +0200 [thread overview]
Message-ID: <20250410-nvmet-fcloop-v4-10-7e5c42b7b2cb@kernel.org> (raw)
In-Reply-To: <20250410-nvmet-fcloop-v4-0-7e5c42b7b2cb@kernel.org>
The lifetime of the fcloop_lsreq is not tight to the lifetime of the
host or target port, thus there is no need anymore to synchronize the
cleanup path anymore.
Signed-off-by: Daniel Wagner <wagi@kernel.org>
---
drivers/nvme/target/fcloop.c | 21 ++++-----------------
1 file changed, 4 insertions(+), 17 deletions(-)
diff --git a/drivers/nvme/target/fcloop.c b/drivers/nvme/target/fcloop.c
index 47ce51183a66b4b37fc850cced2ddf70be2cdb42..ca11230bffedb0f2313a99e24e54e892daf0d644 100644
--- a/drivers/nvme/target/fcloop.c
+++ b/drivers/nvme/target/fcloop.c
@@ -207,7 +207,6 @@ static LIST_HEAD(fcloop_nports);
struct fcloop_lport {
struct nvme_fc_local_port *localport;
struct list_head lport_list;
- struct completion unreg_done;
refcount_t ref;
};
@@ -1083,9 +1082,6 @@ fcloop_localport_delete(struct nvme_fc_local_port *localport)
struct fcloop_lport_priv *lport_priv = localport->private;
struct fcloop_lport *lport = lport_priv->lport;
- /* release any threads waiting for the unreg to complete */
- complete(&lport->unreg_done);
-
fcloop_lport_put(lport);
}
@@ -1238,18 +1234,9 @@ fcloop_create_local_port(struct device *dev, struct device_attribute *attr,
}
static int
-__wait_localport_unreg(struct fcloop_lport *lport)
+__localport_unreg(struct fcloop_lport *lport)
{
- int ret;
-
- init_completion(&lport->unreg_done);
-
- ret = nvme_fc_unregister_localport(lport->localport);
-
- if (!ret)
- wait_for_completion(&lport->unreg_done);
-
- return ret;
+ return nvme_fc_unregister_localport(lport->localport);
}
static struct fcloop_nport *
@@ -1332,7 +1319,7 @@ fcloop_delete_local_port(struct device *dev, struct device_attribute *attr,
if (!lport)
return -ENOENT;
- ret = __wait_localport_unreg(lport);
+ ret = __localport_unreg(lport);
fcloop_lport_put(lport);
return ret ? ret : count;
@@ -1776,7 +1763,7 @@ static void __exit fcloop_exit(void)
spin_unlock_irqrestore(&fcloop_lock, flags);
- ret = __wait_localport_unreg(lport);
+ ret = __localport_unreg(lport);
if (ret)
pr_warn("%s: Failed deleting local port\n", __func__);
--
2.49.0
next prev parent reply other threads:[~2025-04-10 11:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 11:41 [PATCH v4 00/14] nvmet-fcloop: track resources via reference counting Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 01/14] nvmet-fcloop: track ref counts for nports Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 02/14] nvmet-fcloop: remove nport from list on last user Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 03/14] nvmet-fcloop: refactor fcloop_nport_alloc and track lport Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 04/14] nvmet-fcloop: refactor fcloop_delete_local_port Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 05/14] nvmet-fcloop: update refs on tfcp_req Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 06/14] nvmet-fcloop: add missing fcloop_callback_host_done Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 07/14] nvmet-fcloop: access fcpreq only when holding reqlock Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 08/14] nvmet-fcloop: prevent double port deletion Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 09/14] nvmet-fcloop: allocate/free fcloop_lsreq directly Daniel Wagner
2025-04-10 11:41 ` Daniel Wagner [this message]
2025-04-10 11:41 ` [PATCH v4 11/14] nvmet-fcloop: drop response if targetport is gone Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 12/14] nvmet-fc: free pending reqs on tgtport unregister Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 13/14] nvmet-fc: take tgtport refs for portentry Daniel Wagner
2025-04-10 11:41 ` [PATCH v4 14/14] nvme-fc: do not reference lsrsp after failure 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=20250410-nvmet-fcloop-v4-10-7e5c42b7b2cb@kernel.org \
--to=wagi@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®