From: Nix <nix@esperi.org.uk>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Khalid Aziz <khalid@gonehiking.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>,
Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] scsi: Set allocation length to 255 for ATA Information VPD page
Date: Thu, 15 Apr 2021 13:42:02 +0100 [thread overview]
Message-ID: <878s5joh2d.fsf@esperi.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2104141306130.44318@angie.orcam.me.uk> (Maciej W. Rozycki's message of "Thu, 15 Apr 2021 00:39:28 +0200 (CEST)")
On 14 Apr 2021, Maciej W. Rozycki stated:
> Set the allocation length to 255 for the ATA Information VPD page
> requested in the WRITE SAME handler, so as not to limit information
> examined by `scsi_get_vpd_page' in the supported vital product data
> pages unnecessarily.
>
> Originally it was thought that Areca hardware may have issues with a
> valid allocation length supplied for a VPD inquiry, however older SCSI
> standard revisions[1] consider 255 the maximum length allowed and what
Aaaah. That explains a lot! (Not that I can remember what SCSI standard
rev that Areca firmware claimed to implement. I know I never updated the
firmware, so it's going to be something no newer than mid-2009 and
probably quite a bit older.)
> Nix,
>
> I can see you're still around. Would you therefore please be so kind
> as to verify this change with your Areca hardware if you still have it?
It's been up in the loft for years, but I'll get it out this weekend and
give it a spin :) this'll let me make sure the disks still spin as well,
which matters for an in-case-of-lightning-strike disaster-recovery
backup box.
(I just hope this kernel boots on it at all. It's about three years
since I retired it... let's see!)
> It looks to me like you were thinking in the right direction with:
> <https://lore.kernel.org/linux-scsi/87vc3nuipg.fsf@spindle.srvr.nix/>.
It's the sort of mistake I could see myself making: an easy mistake to
make when so many things in C require buffer size - 1 or you get a
disastrous security hole...
--
NULL && (void)
next prev parent reply other threads:[~2021-04-15 13:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 22:38 [PATCH 0/5] Bring the BusLogic host bus adapter driver up to Y2021 Maciej W. Rozycki
2021-04-14 22:39 ` [PATCH 1/5] scsi: BusLogic: Fix missing `pr_cont' use Maciej W. Rozycki
2021-04-16 2:08 ` Joe Perches
2021-04-16 10:48 ` Maciej W. Rozycki
2021-04-16 14:02 ` Joe Perches
2021-04-16 14:28 ` Maciej W. Rozycki
2021-04-16 15:12 ` Joe Perches
2021-04-17 11:39 ` David Laight
2021-04-17 14:01 ` Maciej W. Rozycki
2021-04-16 20:41 ` Khalid Aziz
2021-04-17 0:09 ` Joe Perches
2021-04-16 19:34 ` Khalid Aziz
2021-04-14 22:39 ` [PATCH 2/5] scsi: BusLogic: Avoid unbounded `vsprintf' use Maciej W. Rozycki
2021-04-16 19:54 ` Khalid Aziz
2021-04-14 22:39 ` [PATCH 3/5] scsi: Provide for avoiding trailing allocation length with VPD inquiries Maciej W. Rozycki
2021-04-14 22:39 ` [PATCH 4/5] scsi: Avoid using reserved length byte " Maciej W. Rozycki
2021-04-14 22:39 ` [PATCH 5/5] scsi: Set allocation length to 255 for ATA Information VPD page Maciej W. Rozycki
2021-04-15 12:42 ` Nix [this message]
2021-04-16 15:18 ` Maciej W. Rozycki
2021-04-16 19:36 ` [PATCH 0/5] Bring the BusLogic host bus adapter driver up to Y2021 Khalid Aziz
2021-04-16 21:25 ` Maciej W. Rozycki
2021-04-18 20:21 ` Ondrej Zary
2021-04-19 15:06 ` Khalid Aziz
2021-04-19 16:01 ` Maciej W. Rozycki
2021-04-20 2:16 ` Khalid Aziz
2021-04-20 18:02 ` Maciej W. Rozycki
2021-04-22 2:36 ` Khalid Aziz
2021-04-22 16:27 ` Maciej W. Rozycki
2021-04-22 18:07 ` Khalid Aziz
2021-04-22 23:19 ` Maciej W. Rozycki
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=878s5joh2d.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=bernd.schubert@itwm.fraunhofer.de \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=khalid@gonehiking.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).