From: Benjamin Marzinski <bmarzins@redhat.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
device-mapper development <dm-devel@lists.linux.dev>,
Martin Wilck <Martin.Wilck@suse.com>
Subject: Re: [PATCH] libmultipath: Handle SCSI-2 style vpd page 0x83 descriptors
Date: Tue, 7 Apr 2026 11:13:43 -0400 [thread overview]
Message-ID: <adUfJ-iJVpUZuJrL@redhat.com> (raw)
In-Reply-To: <36483a48-bf89-42da-be3d-303f3560d2d7@gmail.com>
On Tue, Apr 07, 2026 at 11:14:34AM +0200, Xose Vazquez Perez wrote:
> On 3/27/26 4:41 AM, Benjamin Marzinski wrote:
>
> > Some older SCSI devices return a SCSI-2 style vpd page 0x83, instead of
> > a SPC-2/3 format one. The SCSI-2 page 83 format returns an IEEE WWN in
> > binary encoded hexi-decimal in the 16 bytes following the initial
> > 4-byte page 83 reply header.
> >
> > Check the 7th byte of the vpd page 83 buffer to determine whether this
> > is a SCSI-2 or SPC-2/3 confomant one. Byte 7 is the 3rd byte of first
> > Identification descriptor in a SPC-2/3 confromant vpd page 83. This is a
> > reserved field, and is guaranteed to be 0. If it is not zero, then it is
> > likely the 3rd byte of a SCSI-2 Identifier (The first 3 bytes of the ID
> > are the Organizationally Unique Identifier). Both the sg_inq and scsi_id
> > commands handle vpd page 83 this way. To make sure that the WWID which
> > multipath reads directly from the device matches, it should handle this
> > format as well.
> Out of curiosity. Did you run into a specific old device that triggered this,
> or was this found by code inspection ?
It was through code inspection.
-Ben
next prev parent reply other threads:[~2026-04-07 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 3:41 [PATCH] libmultipath: Handle SCSI-2 style vpd page 0x83 descriptors Benjamin Marzinski
2026-04-07 9:14 ` Xose Vazquez Perez
2026-04-07 15:13 ` Benjamin Marzinski [this message]
2026-04-13 11:11 ` Martin Wilck
2026-04-13 16:15 ` Benjamin Marzinski
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=adUfJ-iJVpUZuJrL@redhat.com \
--to=bmarzins@redhat.com \
--cc=Martin.Wilck@suse.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=xose.vazquez@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.