Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: kbusch@kernel.org, sagi@grimberg.me, fancer.lancer@gmail.com,
	linux@roeck-us.net
Cc: linux-nvme@lists.infradead.org
Subject: [PATCH] nvme-hwmon: don't return errors from nvme_hwmon_init
Date: Tue, 18 Oct 2022 16:58:08 +0200	[thread overview]
Message-ID: <20221018145808.681327-1-hch@lst.de> (raw)

An NVMe controller works perfectly fine even when the hwmon
initialization fails.  Stop returning errors from nvme_hwmon_init to
handle this case consistently.

Signed-off-by: Christoph Hellwig <hch@lst.de>
---

This should go before the patch from Serge to document and consistently
handle the lack of initialization failure handling for hwmon.

 drivers/nvme/host/core.c  |  7 ++-----
 drivers/nvme/host/hwmon.c | 16 +++++++++-------
 drivers/nvme/host/nvme.h  |  5 ++---
 3 files changed, 13 insertions(+), 15 deletions(-)

diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 9cbe7854d4883..952768966bdcd 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -3261,11 +3261,8 @@ int nvme_init_ctrl_finish(struct nvme_ctrl *ctrl)
 	if (ret < 0)
 		return ret;
 
-	if (!ctrl->identified && !nvme_discovery_ctrl(ctrl)) {
-		ret = nvme_hwmon_init(ctrl);
-		if (ret < 0)
-			return ret;
-	}
+	if (!ctrl->identified && !nvme_discovery_ctrl(ctrl))
+		nvme_hwmon_init(ctrl);
 
 	ctrl->identified = true;
 
diff --git a/drivers/nvme/host/hwmon.c b/drivers/nvme/host/hwmon.c
index 0a586d7129201..c6ddb8b46c699 100644
--- a/drivers/nvme/host/hwmon.c
+++ b/drivers/nvme/host/hwmon.c
@@ -221,7 +221,8 @@ static const struct hwmon_chip_info nvme_hwmon_chip_info = {
 	.info	= nvme_hwmon_info,
 };
 
-int nvme_hwmon_init(struct nvme_ctrl *ctrl)
+/* do not return errors - nvme works fine without hwmon registration */
+void nvme_hwmon_init(struct nvme_ctrl *ctrl)
 {
 	struct device *dev = ctrl->device;
 	struct nvme_hwmon_data *data;
@@ -230,7 +231,7 @@ int nvme_hwmon_init(struct nvme_ctrl *ctrl)
 
 	data = kzalloc(sizeof(*data), GFP_KERNEL);
 	if (!data)
-		return 0;
+		return;
 
 	data->ctrl = ctrl;
 	mutex_init(&data->read_lock);
@@ -238,8 +239,7 @@ int nvme_hwmon_init(struct nvme_ctrl *ctrl)
 	err = nvme_hwmon_get_smart_log(data);
 	if (err) {
 		dev_warn(dev, "Failed to read smart log (error %d)\n", err);
-		kfree(data);
-		return err;
+		goto out_free_data;
 	}
 
 	hwmon = hwmon_device_register_with_info(dev, "nvme",
@@ -247,11 +247,13 @@ int nvme_hwmon_init(struct nvme_ctrl *ctrl)
 						NULL);
 	if (IS_ERR(hwmon)) {
 		dev_warn(dev, "Failed to instantiate hwmon device\n");
-		kfree(data);
-		return PTR_ERR(hwmon);
+		goto out_free_data;
 	}
 	ctrl->hwmon_device = hwmon;
-	return 0;
+	return;
+
+out_free_data:
+	kfree(data);
 }
 
 void nvme_hwmon_exit(struct nvme_ctrl *ctrl)
diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
index a29877217ee65..4cd3e00c47a2b 100644
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -1000,12 +1000,11 @@ static inline struct nvme_ns *nvme_get_ns_from_dev(struct device *dev)
 }
 
 #ifdef CONFIG_NVME_HWMON
-int nvme_hwmon_init(struct nvme_ctrl *ctrl);
+void nvme_hwmon_init(struct nvme_ctrl *ctrl);
 void nvme_hwmon_exit(struct nvme_ctrl *ctrl);
 #else
-static inline int nvme_hwmon_init(struct nvme_ctrl *ctrl)
+static inline void nvme_hwmon_init(struct nvme_ctrl *ctrl)
 {
-	return 0;
 }
 
 static inline void nvme_hwmon_exit(struct nvme_ctrl *ctrl)
-- 
2.30.2



             reply	other threads:[~2022-10-18 14:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 14:58 Christoph Hellwig [this message]
2022-10-18 15:14 ` [PATCH] nvme-hwmon: don't return errors from nvme_hwmon_init Serge Semin
2022-10-18 15:16   ` Christoph Hellwig
2022-10-18 15:21     ` Serge Semin
2022-10-18 15:23       ` Christoph Hellwig
2022-10-18 15:25         ` Serge Semin
2022-10-18 15:15 ` Keith Busch
2022-10-18 15:23   ` Christoph Hellwig
2022-10-18 15:26     ` Keith Busch
2022-10-18 15:31       ` Christoph Hellwig
2022-10-18 15:31       ` Serge Semin
2022-10-18 15:38         ` Christoph Hellwig
2022-10-18 15:44           ` Serge Semin

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=20221018145808.681327-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=fancer.lancer@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --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