From: Brian Bunker <brian@purestorage.com>
To: linux-scsi@vger.kernel.org, hare@suse.com
Cc: Brian Bunker <brian@purestorage.com>,
Krishna Kant <krishna.kant@purestorage.com>,
Riya Savla <rsavla@purestorage.com>
Subject: [PATCH v2] scsi: scsi_dh_alua: use the device timeout rather than a constant
Date: Wed, 25 Mar 2026 08:15:15 -0700 [thread overview]
Message-ID: <20260325151515.18688-2-brian@purestorage.com> (raw)
In-Reply-To: <20260325151515.18688-1-brian@purestorage.com>
Instead of using a constant for timeouts, use the timeout of the SCSI
device itself. There are reasons why someone might want to extend
the SCSI timeout and having the constant out of sync can lead to
early timeouts.
Signed-off-by: Krishna Kant <krishna.kant@purestorage.com>
Signed-off-by: Riya Savla <rsavla@purestorage.com>
Signed-off-by: Brian Bunker <brian@purestorage.com>
---
drivers/scsi/device_handler/scsi_dh_alua.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/scsi/device_handler/scsi_dh_alua.c b/drivers/scsi/device_handler/scsi_dh_alua.c
index efb08b9b145a..a4ee67109548 100644
--- a/drivers/scsi/device_handler/scsi_dh_alua.c
+++ b/drivers/scsi/device_handler/scsi_dh_alua.c
@@ -143,7 +143,7 @@ static int submit_rtpg(struct scsi_device *sdev, unsigned char *buff,
put_unaligned_be32(bufflen, &cdb[6]);
return scsi_execute_cmd(sdev, cdb, opf, buff, bufflen,
- ALUA_FAILOVER_TIMEOUT * HZ,
+ READ_ONCE(sdev->request_queue->rq_timeout) ?: ALUA_FAILOVER_TIMEOUT * HZ,
ALUA_FAILOVER_RETRIES, &exec_args);
}
@@ -178,7 +178,7 @@ static int submit_stpg(struct scsi_device *sdev, int group_id,
put_unaligned_be32(stpg_len, &cdb[6]);
return scsi_execute_cmd(sdev, cdb, opf, stpg_data,
- stpg_len, ALUA_FAILOVER_TIMEOUT * HZ,
+ stpg_len, READ_ONCE(sdev->request_queue->rq_timeout) ?: ALUA_FAILOVER_TIMEOUT * HZ,
ALUA_FAILOVER_RETRIES, &exec_args);
}
@@ -512,7 +512,7 @@ static int alua_tur(struct scsi_device *sdev)
struct scsi_sense_hdr sense_hdr;
int retval;
- retval = scsi_test_unit_ready(sdev, ALUA_FAILOVER_TIMEOUT * HZ,
+ retval = scsi_test_unit_ready(sdev, READ_ONCE(sdev->request_queue->rq_timeout) ?: ALUA_FAILOVER_TIMEOUT * HZ,
ALUA_FAILOVER_RETRIES, &sense_hdr);
if ((sense_hdr.sense_key == NOT_READY ||
sense_hdr.sense_key == UNIT_ATTENTION) &&
@@ -552,7 +552,8 @@ static int alua_rtpg(struct scsi_device *sdev, struct alua_port_group *pg)
valid_states_old = pg->valid_states;
if (!pg->expiry) {
- unsigned long transition_tmo = ALUA_FAILOVER_TIMEOUT * HZ;
+ unsigned long transition_tmo = min(READ_ONCE(sdev->request_queue->rq_timeout) ?: ALUA_FAILOVER_TIMEOUT * HZ,
+ (unsigned long)U8_MAX * HZ);
if (pg->transition_tmo)
transition_tmo = pg->transition_tmo * HZ;
@@ -664,7 +665,8 @@ static int alua_rtpg(struct scsi_device *sdev, struct alua_port_group *pg)
if ((buff[4] & RTPG_FMT_MASK) == RTPG_FMT_EXT_HDR && buff[5] != 0)
pg->transition_tmo = buff[5];
else
- pg->transition_tmo = ALUA_FAILOVER_TIMEOUT;
+ pg->transition_tmo = min((READ_ONCE(sdev->request_queue->rq_timeout) ?: ALUA_FAILOVER_TIMEOUT * HZ) / HZ,
+ (unsigned long)U8_MAX);
if (orig_transition_tmo != pg->transition_tmo) {
sdev_printk(KERN_INFO, sdev,
--
2.50.1 (Apple Git-155)
next prev parent reply other threads:[~2026-03-25 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 15:15 [PATCH v2 0/1] scsi: scsi_dh_alua: use device timeout instead of constant Brian Bunker
2026-03-25 15:15 ` Brian Bunker [this message]
2026-03-26 10:22 ` [PATCH v2] scsi: scsi_dh_alua: use the device timeout rather than a constant Hannes Reinecke
2026-03-27 0:12 ` Brian Bunker
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=20260325151515.18688-2-brian@purestorage.com \
--to=brian@purestorage.com \
--cc=hare@suse.com \
--cc=krishna.kant@purestorage.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rsavla@purestorage.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