From: Tzung-Bi Shih <tzungbi@kernel.org>
To: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
tzungbi@kernel.org
Subject: [PATCH] scsi: core: Don't free dev_name() manually
Date: Sun, 18 Jan 2026 03:32:21 +0800 [thread overview]
Message-ID: <20260117193221.152540-1-tzungbi@kernel.org> (raw)
scsi_host_alloc() is designed to hold initial reference count of
`&shost->shost_gendev` and `&shost->shost_dev`. In the error handling
paths [1], only drop a reference count to `&shost->shost_gendev` is
sufficient as scsi_host_dev_release() will be called and the reference
count of `&shost->shost_dev` should be dropped at that time.
Drivers shouldn't need to free the device name and hold a reference
count to its parent device as the driver core automatically handles
that. Remove them.
[1] Either at "fail" label in scsi_host_alloc() or in SCSI drivers that
a subsequent scsi_add_host{,_with_dma}() fails.
Fixes: b49493f99690 ("Fix a memory leak in scsi_host_dev_release()")
Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
---
drivers/scsi/hosts.c | 16 +++++-----------
1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/drivers/scsi/hosts.c b/drivers/scsi/hosts.c
index 1b3fbd328277..b88d553cdde6 100644
--- a/drivers/scsi/hosts.c
+++ b/drivers/scsi/hosts.c
@@ -55,7 +55,6 @@ static DEFINE_IDA(host_index_ida);
static void scsi_host_cls_release(struct device *dev)
{
- put_device(&class_to_shost(dev)->shost_gendev);
}
static struct class shost_class = {
@@ -279,11 +278,9 @@ int scsi_add_host_with_dma(struct Scsi_Host *shost, struct device *dev,
goto out_disable_runtime_pm;
scsi_host_set_state(shost, SHOST_RUNNING);
- get_device(shost->shost_gendev.parent);
device_enable_async_suspend(&shost->shost_dev);
- get_device(&shost->shost_gendev);
error = device_add(&shost->shost_dev);
if (error)
goto out_del_gendev;
@@ -352,7 +349,6 @@ EXPORT_SYMBOL(scsi_add_host_with_dma);
static void scsi_host_dev_release(struct device *dev)
{
struct Scsi_Host *shost = dev_to_shost(dev);
- struct device *parent = dev->parent;
/* Wait for functions invoked through call_rcu(&scmd->rcu, ...) */
rcu_barrier();
@@ -366,22 +362,20 @@ static void scsi_host_dev_release(struct device *dev)
if (shost->shost_state == SHOST_CREATED) {
/*
- * Free the shost_dev device name and remove the proc host dir
+ * Drop the reference to shost_dev and remove the proc host dir
* here if scsi_host_{alloc,put}() have been called but neither
- * scsi_host_add() nor scsi_remove_host() has been called.
+ * scsi_add_host() nor scsi_remove_host() has been called.
* This avoids that the memory allocated for the shost_dev
* name as well as the proc dir structure are leaked.
*/
scsi_proc_hostdir_rm(shost->hostt);
- kfree(dev_name(&shost->shost_dev));
+ put_device(&shost->shost_dev);
}
kfree(shost->shost_data);
ida_free(&host_index_ida, shost->host_no);
- if (shost->shost_state != SHOST_CREATED)
- put_device(parent);
kfree(shost);
}
@@ -550,8 +544,8 @@ struct Scsi_Host *scsi_host_alloc(const struct scsi_host_template *sht, int priv
fail:
/*
* Host state is still SHOST_CREATED and that is enough to release
- * ->shost_gendev. scsi_host_dev_release() will free
- * dev_name(&shost->shost_dev).
+ * ->shost_gendev. scsi_host_dev_release() will
+ * put_device(&shost->shost_dev).
*/
put_device(&shost->shost_gendev);
--
2.48.1
next reply other threads:[~2026-01-17 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 19:32 Tzung-Bi Shih [this message]
2026-01-18 14:45 ` [PATCH] scsi: core: Don't free dev_name() manually James Bottomley
2026-01-19 14:28 ` Tzung-Bi Shih
2026-01-19 16:02 ` James Bottomley
2026-01-20 13:11 ` Tzung-Bi Shih
2026-01-20 14:26 ` James Bottomley
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=20260117193221.152540-1-tzungbi@kernel.org \
--to=tzungbi@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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