From: Tyler Erickson <tyler.erickson@seagate.com>
To: damien.lemoal@opensource.wdc.com, jejb@linux.ibm.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
muhammad.ahmad@seagate.com, tyler.erickson@seagate.com
Subject: [PATCH 0/2] ata,sd: Fix reading concurrent positioning ranges
Date: Tue, 31 May 2022 11:50:07 -0600 [thread overview]
Message-ID: <20220531175009.850-1-tyler.erickson@seagate.com> (raw)
This patch series fixes reading the concurrent positioning ranges.
The first patch fixes reading this in libata, where it was reading
more data than a drive necessarily supports, resulting in a
command abort. There was also a change to the SCSI translated
data to put the VPD page length in the correct starting byte.
In sd, the fix is adding 4 instead of 3 for the header length.
Using 3 will always result in an error and was likely used incorrectly
as T10 specifications list all tables starting at byte 0, and byte 3 is
the page length, which would mean there are 4 total bytes before the
remaining data that contains the ranges and other information.
Tyler Erickson (2):
libata: fix reading concurrent positioning ranges log
sd: Fixing interpretation of VPD B9h length
drivers/ata/libata-core.c | 21 +++++++++++++--------
drivers/ata/libata-scsi.c | 2 +-
drivers/scsi/sd.c | 2 +-
3 files changed, 15 insertions(+), 10 deletions(-)
base-commit: af2d861d4cd2a4da5137f795ee3509e6f944a25b
--
2.25.1
next reply other threads:[~2022-05-31 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 17:50 Tyler Erickson [this message]
2022-05-31 17:50 ` [PATCH 1/2] [PATCH v1 1/2] libata: fix reading concurrent positioning ranges log Tyler Erickson
2022-05-31 21:28 ` Damien Le Moal
2022-06-01 10:29 ` Sergey Shtylyov
2022-06-02 6:35 ` Damien Le Moal
2022-05-31 17:50 ` [PATCH 2/2] [PATCH v1 2/2] sd: Fixing interpretation of VPD B9h length Tyler Erickson
2022-05-31 21:30 ` Damien Le Moal
2022-05-31 21:57 ` Tyler Erickson
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=20220531175009.850-1-tyler.erickson@seagate.com \
--to=tyler.erickson@seagate.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jejb@linux.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=muhammad.ahmad@seagate.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