From: "Martin K. Petersen" <mkp@kernel.org>
To: Brian Bunker <brian@purestorage.com>
Cc: linux-scsi@vger.kernel.org,
"Martin K . Petersen" <mkp@kernel.org>,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
Hannes Reinecke <hare@kernel.org>,
Bart Van Assche <bvanassche@acm.org>,
Krishna Kant <krishna.kant@purestorage.com>
Subject: Re: [PATCH v3 0/3] scsi: Bind sd to LUs in the ALUA unavailable state
Date: Sun, 08 Nov 2026 22:02:45 -0500 [thread overview]
Message-ID: <yq1wlqmwvug.fsf@mail.kernel.org> (raw)
In-Reply-To: <20261029002531.82824-1-brian@purestorage.com>
Brian,
> A LU that is in the ALUA unavailable state on a target port reports
> peripheral qualifier 001b in its INQUIRY data. scsi_bus_match() only
> matches devices with peripheral qualifier 000b, so if a host scans
> such a path, no upper-level driver is ever bound to it. When the
> target port later becomes available, nothing binds sd and the path
> stays unusable until the device is deleted and rescanned. A host that
> was already running when the path became unavailable keeps sd bound,
> so the result depends on when the host scanned.
Applied to 7.5/scsi-staging, thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2026-11-09 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 0:25 [PATCH v3 0/3] scsi: Bind sd to LUs in the ALUA unavailable state Brian Bunker
2026-10-29 0:25 ` [PATCH v3 1/3] scsi: core: Move REPORT TARGET PORT GROUPS into the SCSI core Brian Bunker
2026-10-29 8:54 ` Hannes Reinecke
2026-10-29 0:25 ` [PATCH v3 2/3] scsi: core: Read the ALUA access state when a device is scanned Brian Bunker
2026-10-29 8:55 ` Hannes Reinecke
2026-10-29 0:25 ` [PATCH v3 3/3] scsi: core: Match ULDs to logical units in the ALUA unavailable state Brian Bunker
2026-10-29 8:56 ` Hannes Reinecke
2026-11-09 3:02 ` Martin K. Petersen [this message]
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=yq1wlqmwvug.fsf@mail.kernel.org \
--to=mkp@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=brian@purestorage.com \
--cc=bvanassche@acm.org \
--cc=hare@kernel.org \
--cc=krishna.kant@purestorage.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