From: Keith Busch <kbusch@meta.com>
To: <linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, <sagi@grimberg.me>, <mlombard@redhat.com>,
<hare@suse.de>, <shinichiro.kawasaki@wdc.com>,
Keith Busch <kbusch@kernel.org>
Subject: [PATCH-RFC 2/5] nvme: tcp: split controller bringup handling
Date: Mon, 3 Jun 2024 16:05:20 -0700 [thread overview]
Message-ID: <20240603230524.3854115-3-kbusch@meta.com> (raw)
In-Reply-To: <20240603230524.3854115-1-kbusch@meta.com>
From: Keith Busch <kbusch@kernel.org>
Drivers must call nvme_uninit_ctrl after a successful nvme_init_ctrl.
Split the allocation side out to make the error handling boundary easier
to navigate. The nvme tcp driver's error handling had different returns
in the error goto labels, which harm readability.
Signed-off-by: Keith Busch <kbusch@kernel.org>
---
drivers/nvme/host/tcp.c | 25 +++++++++++++++++++------
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
index 8b5e4327fe83b..7f75d01dcbed0 100644
--- a/drivers/nvme/host/tcp.c
+++ b/drivers/nvme/host/tcp.c
@@ -2686,7 +2686,7 @@ nvme_tcp_existing_controller(struct nvmf_ctrl_options *opts)
return found;
}
-static struct nvme_ctrl *nvme_tcp_create_ctrl(struct device *dev,
+static struct nvme_tcp_ctrl *nvme_tcp_alloc_ctrl(struct device *dev,
struct nvmf_ctrl_options *opts)
{
struct nvme_tcp_ctrl *ctrl;
@@ -2761,6 +2761,24 @@ static struct nvme_ctrl *nvme_tcp_create_ctrl(struct device *dev,
if (ret)
goto out_kfree_queues;
+ return ctrl;
+out_kfree_queues:
+ kfree(ctrl->queues);
+out_free_ctrl:
+ kfree(ctrl);
+ return ERR_PTR(ret);
+}
+
+static struct nvme_ctrl *nvme_tcp_create_ctrl(struct device *dev,
+ struct nvmf_ctrl_options *opts)
+{
+ struct nvme_tcp_ctrl *ctrl;
+ int ret;
+
+ ctrl = nvme_tcp_alloc_ctrl(dev, opts);
+ if (IS_ERR(ctrl))
+ return (struct nvme_ctrl *)ctrl;
+
if (!nvme_change_ctrl_state(&ctrl->ctrl, NVME_CTRL_CONNECTING)) {
WARN_ON_ONCE(1);
ret = -EINTR;
@@ -2786,11 +2804,6 @@ static struct nvme_ctrl *nvme_tcp_create_ctrl(struct device *dev,
if (ret > 0)
ret = -EIO;
return ERR_PTR(ret);
-out_kfree_queues:
- kfree(ctrl->queues);
-out_free_ctrl:
- kfree(ctrl);
- return ERR_PTR(ret);
}
static struct nvmf_transport_ops nvme_tcp_transport = {
--
2.43.0
next prev parent reply other threads:[~2024-06-03 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 23:05 [PATCH-RFC 0/5] nvme: fix initialization memleak Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 1/5] nvme: apple: fix device reference counting Keith Busch
2024-06-03 23:17 ` Keith Busch
2024-06-03 23:05 ` Keith Busch [this message]
2024-06-04 0:35 ` [PATCH-RFC 2/5] nvme: tcp: split controller bringup handling Caleb Sander
2024-06-04 2:44 ` Keith Busch
2024-06-04 4:23 ` Christoph Hellwig
2024-06-04 6:47 ` Hannes Reinecke
2024-06-03 23:05 ` [PATCH-RFC 3/5] nvme: rdma: " Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 4/5] nvme: fc: " Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 5/5] nvme: split device add from initialzation Keith Busch
2024-06-04 4:24 ` [PATCH-RFC 0/5] nvme: fix initialization memleak Christoph Hellwig
2024-06-04 14:51 ` Sagi Grimberg
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=20240603230524.3854115-3-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.com \
--cc=sagi@grimberg.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox