From: <dan.carpenter@oracle.com>
To: don.brace@microsemi.com
Cc: esc.storagedev@microsemi.com, linux-scsi@vger.kernel.org
Subject: [bug report] scsi: hpsa: Increase controller error handling timeout
Date: Mon, 27 Jul 2020 14:19:16 +0300 [thread overview]
Message-ID: <20200727111916.GC389488@mwanda> (raw)
Hello Don Brace,
The patch c73deaf3b001: "scsi: hpsa: Increase controller error
handling timeout" from Jul 20, 2020, leads to the following static
checker warning:
drivers/scsi/hpsa.c:2163 hpsa_slave_configure()
error: uninitialized symbol 'queue_depth'.
drivers/scsi/hpsa.c
2136 /* configure scsi device based on internal per-device structure */
2137 #define CTLR_TIMEOUT (120 * HZ)
2138 static int hpsa_slave_configure(struct scsi_device *sdev)
2139 {
2140 struct hpsa_scsi_dev_t *sd;
2141 int queue_depth;
^^^^^^^^^^^^^^^
2142
2143 sd = sdev->hostdata;
2144 sdev->no_uld_attach = !sd || !sd->expose_device;
2145
2146 if (sd) {
2147 sd->was_removed = 0;
2148 if (sd->external) {
2149 queue_depth = EXTERNAL_QD;
2150 sdev->eh_timeout = HPSA_EH_PTRAID_TIMEOUT;
2151 blk_queue_rq_timeout(sdev->request_queue,
2152 HPSA_EH_PTRAID_TIMEOUT);
2153 } else if (is_hba_lunid(sd->scsi3addr)) {
2154 sdev->eh_timeout = CTLR_TIMEOUT;
2155 blk_queue_rq_timeout(sdev->request_queue, CTLR_TIMEOUT);
Not set on this path.
2156 } else {
2157 queue_depth = sd->queue_depth != 0 ?
2158 sd->queue_depth : sdev->host->can_queue;
2159 }
2160 } else
2161 queue_depth = sdev->host->can_queue;
2162
2163 scsi_change_queue_depth(sdev, queue_depth);
^^^^^^^^^^^
2164
2165 return 0;
2166 }
regards,
dan carpenter
next reply other threads:[~2020-07-27 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 11:19 dan.carpenter [this message]
2020-07-27 14:31 ` [bug report] scsi: hpsa: Increase controller error handling timeout Don.Brace
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=20200727111916.GC389488@mwanda \
--to=dan.carpenter@oracle.com \
--cc=don.brace@microsemi.com \
--cc=esc.storagedev@microsemi.com \
--cc=linux-scsi@vger.kernel.org \
/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