[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221017171147.3300575-1-khazhy@google.com>
Date: Mon, 17 Oct 2022 10:11:47 -0700
From: Khazhismel Kumykov <khazhy@...omium.org>
To: "James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Cc: Gabriel Krisman Bertazi <krisman@...labora.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
Khazhismel Kumykov <khazhy@...gle.com>
Subject: [PATCH] scsi: fix crash in scsi_remove_host after alloc failure
If transport_register_device returns error, shost_gendev has already
been cleaned up - however since we ignore the error device setup
continues happily. We will eventually call transport_unregister_device,
attempting to delete shost_gendev again, resulting in a crash.
It looks like when this cleanup behavior was added, iscsi was updated,
but scsi was missed.
Fixes: cd7ea70bb00a ("scsi: drivers: base: Propagate errors through the transport component")
Signed-off-by: Khazhismel Kumykov <khazhy@...gle.com>
---
drivers/scsi/scsi_sysfs.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index c95177ca6ed2..722ab042fbd7 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1599,7 +1599,11 @@ EXPORT_SYMBOL(scsi_register_interface);
**/
int scsi_sysfs_add_host(struct Scsi_Host *shost)
{
- transport_register_device(&shost->shost_gendev);
+ int err;
+
+ err = transport_register_device(&shost->shost_gendev);
+ if (err)
+ return err;
transport_configure_device(&shost->shost_gendev);
return 0;
}
--
2.38.0.413.g74048e4d9e-goog
Powered by blists - more mailing lists