From: Lee Duncan <lduncan@suse.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Lee Duncan <leeman.duncan@gmail.com>,
Linux regressions mailing list <regressions@lists.linux.dev>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Wilck <mwilck@suse.com>, Hannes Reinecke <hare@suse.de>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Subject: Re: [PATCH] scsi: core: Add BLIST_NO_ASK_VPD_SIZE for some VDASD
Date: Wed, 8 Mar 2023 10:41:51 -0800 [thread overview]
Message-ID: <a4ecf9eb-509a-84a6-8a9f-a3f5ea54ecac@suse.com> (raw)
In-Reply-To: <yq1edq0jg2h.fsf@ca-mkp.ca.oracle.com>
On 3/7/23 15:40, Martin K. Petersen wrote:
>
> Lee,
>
>> My worry is that this won't always work. Looking at the code, the
>> buffer sizes used for VPD pages include 8, 32, 64, and 252 bytes. I'm
>> not sure how reading 255 bytes into an 8-byte buffer would work.
>
> In the scsi_get_vpd_buf() case we will allocate a 255 byte buffer since
> that's what scsi_get_vpd_size() returns for a VDASD.
>
> And in the scsi_get_vpd_page() case, where a buffer already exists, we
> clamp the INQUIRY size to the minimum of scsi_get_vpd_size() and the
> buffer length provided by the caller.
>
Please add my Reviewed-by tag then.
--
Lee
next prev parent reply other threads:[~2023-03-08 18:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 18:13 Lee Duncan
2022-09-29 10:42 ` Martin Wilck
2022-10-02 21:16 ` Bart Van Assche
2022-10-02 22:21 ` Lee Duncan
2022-10-04 6:00 ` Hannes Reinecke
2022-11-08 2:50 ` Martin K. Petersen
2022-11-08 6:57 ` Hannes Reinecke
2022-11-21 14:53 ` Martin Wilck
2022-10-03 16:32 ` Bart Van Assche
2023-02-20 11:13 ` Srikar Dronamraju
2023-02-27 7:02 ` Hannes Reinecke
2023-03-03 9:02 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-03 18:54 ` Lee Duncan
2023-03-06 22:14 ` Martin K. Petersen
2023-03-07 2:54 ` Martin K. Petersen
2023-03-07 10:32 ` Srikar Dronamraju
2023-03-07 16:33 ` Lee Duncan
2023-03-07 23:40 ` Martin K. Petersen
2023-03-08 18:41 ` Lee Duncan [this message]
2023-03-10 3:17 ` Martin K. Petersen
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=a4ecf9eb-509a-84a6-8a9f-a3f5ea54ecac@suse.com \
--to=lduncan@suse.com \
--cc=hare@suse.de \
--cc=jejb@linux.ibm.com \
--cc=leeman.duncan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mwilck@suse.com \
--cc=regressions@lists.linux.dev \
--cc=srikar@linux.vnet.ibm.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
Powered by JetHome