From: Matthew Wilcox <matthew@wil.cx>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi core: fix uninitialized variable error
Date: Sun, 5 Feb 2006 08:01:33 -0700 [thread overview]
Message-ID: <20060205150133.GC16090@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0602021637430.4715-100000@iolanthe.rowland.org>
On Thu, Feb 02, 2006 at 04:44:20PM -0500, Alan Stern wrote:
> This patch (as649) fixes an uninitialized variable error (sdev) in
> __scsi_add_device. I don't understand why the compiler didn't flag the
> error.
> @@ -1265,7 +1261,6 @@ struct scsi_device *__scsi_add_device(st
> {
> struct scsi_device *sdev;
> struct device *parent = &shost->shost_gendev;
> - int res;
> struct scsi_target *starget;
>
> starget = scsi_alloc_target(parent, channel, id);
> @@ -1274,12 +1269,10 @@ struct scsi_device *__scsi_add_device(st
>
> get_device(&starget->dev);
> mutex_lock(&shost->scan_mutex);
> - if (scsi_host_scan_allowed(shost)) {
> - res = scsi_probe_and_add_lun(starget, lun, NULL, &sdev, 1,
> - hostdata);
> - if (res != SCSI_SCAN_LUN_PRESENT)
> - sdev = ERR_PTR(-ENODEV);
> - }
> + if (!scsi_host_scan_allowed(shost) ||
> + scsi_probe_and_add_lun(starget, lun, NULL, &sdev, 1,
> + hostdata) != SCSI_SCAN_LUN_PRESENT)
> + sdev = ERR_PTR(-ENODEV);
> mutex_unlock(&shost->scan_mutex);
> scsi_target_reap(starget);
> put_device(&starget->dev);
Seems to me it'd be much easier just to initialise sdev to
ERR_PTR(-ENODEV) at the top of the function. That way, __scsi_add_device
doesn't need to know what the return codes from scsi_probe_and_add_lun
mean. Something like this (untested):
diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
index 752fb5d..4c7bd89 100644
--- a/drivers/scsi/scsi_scan.c
+++ b/drivers/scsi/scsi_scan.c
@@ -1267,9 +1267,8 @@ static int scsi_report_lun_scan(struct s
struct scsi_device *__scsi_add_device(struct Scsi_Host *shost, uint channel,
uint id, uint lun, void *hostdata)
{
- struct scsi_device *sdev;
+ struct scsi_device *sdev = ERR_PTR(-ENODEV);
struct device *parent = &shost->shost_gendev;
- int res;
struct scsi_target *starget;
starget = scsi_alloc_target(parent, channel, id);
@@ -1278,12 +1277,8 @@ struct scsi_device *__scsi_add_device(st
get_device(&starget->dev);
mutex_lock(&shost->scan_mutex);
- if (scsi_host_scan_allowed(shost)) {
- res = scsi_probe_and_add_lun(starget, lun, NULL, &sdev, 1,
- hostdata);
- if (res != SCSI_SCAN_LUN_PRESENT)
- sdev = ERR_PTR(-ENODEV);
- }
+ if (scsi_host_scan_allowed(shost))
+ scsi_probe_and_add_lun(starget, lun, NULL, &sdev, 1, hostdata);
mutex_unlock(&shost->scan_mutex);
scsi_target_reap(starget);
put_device(&starget->dev);
next prev parent reply other threads:[~2006-02-05 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 21:44 [PATCH] scsi core: fix uninitialized variable error Alan Stern
2006-02-05 15:01 ` Matthew Wilcox [this message]
2006-02-05 16:11 ` Alan Stern
2006-02-05 21:30 ` Matthew Wilcox
2006-02-05 21:45 ` Alan Stern
2006-02-06 8:42 ` Markus Lidel
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=20060205150133.GC16090@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).