public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Bunker <brian@purestorage.com>
To: hare@suse.de, linux-scsi@vger.kernel.org
Cc: Brian Bunker <brian@purestorage.com>
Subject: [PATCH v3 0/1] scsi: scsi_dh_alua: increase default ALUA timeout to maximum spec value
Date: Tue, 14 Apr 2026 11:27:47 -0700	[thread overview]
Message-ID: <20260414182748.39776-1-brian@purestorage.com> (raw)

The ALUA handler already maps a 0 value (no implicit transition timeout
provided by the target) to the ALUA_FAILOVER_TIMEOUT constant. This
means the kernel is already saying it won't accept an infinite
transition time - it substitutes a finite default instead.

It has been suggested that some arrays may take tens of minutes to
complete transitions, but even today those would be broken by the
current 0-to-60-second translation. The kernel currently caps this.

The SCSI specification allows the implicit transition timeout to be
specified as a single byte, meaning the maximum explicit value is 255
seconds. This patch simply changes the default from an arbitrary 60
seconds to U8_MAX (255), the highest value that could be explicitly
provided by the target per the spec.

This is a minimal, safe change: we're not removing the cap, just
raising the default to match what the spec allows.

Brian Bunker (1):
  scsi: scsi_dh_alua: increase default ALUA timeout to maximum spec
    value

 drivers/scsi/device_handler/scsi_dh_alua.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.50.1 (Apple Git-155)


             reply	other threads:[~2026-04-14 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 18:27 Brian Bunker [this message]
2026-04-14 18:27 ` [PATCH v3 1/1] scsi: scsi_dh_alua: increase default ALUA timeout to maximum spec value Brian Bunker
2026-04-15  5:59   ` Hannes Reinecke
2026-04-16  6:25     ` Johannes Thumshirn

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=20260414182748.39776-1-brian@purestorage.com \
    --to=brian@purestorage.com \
    --cc=hare@suse.de \
    --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