From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 6/7] scsi-disk: Block Device Characteristics emulation fix
Date: Thu, 12 Jul 2018 18:31:51 +0200 [thread overview]
Message-ID: <20180712163152.12521-7-kwolf@redhat.com> (raw)
In-Reply-To: <20180712163152.12521-1-kwolf@redhat.com>
From: Daniel Henrique Barboza <danielhb413@gmail.com>
The current BDC VPD page (page 0xb1) is too short. This can be
seen running sg_utils:
$ sg_vpd --page=bdc /dev/sda
Block device characteristics VPD page (SBC):
Block device characteristics VPD page length too short=8
By the SCSI spec, the expected size of the SBC page is 0x40.
There is no telling how the guest will behave with a shorter
message - it can ignore it, or worse, make (wrong)
assumptions.
This patch fixes the emulation by setting the size to 0x40.
This is the output of the previous sg_vpd command after
applying it:
$ sg_vpd --page=bdc /dev/sda -v
inquiry cdb: 12 01 b1 00 fc 00
Block device characteristics VPD page (SBC):
[PQual=0 Peripheral device type: disk]
Medium rotation rate is not reported
Product type: Not specified
WABEREQ=0
WACEREQ=0
Nominal form factor not reported
FUAB=0
VBULS=0
To improve readability, this patch also adds the VBULS value
explictly and add comments on the existing fields we're
setting.
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
hw/scsi/scsi-disk.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/scsi-disk.c
index d7df357029..5bb390773b 100644
--- a/hw/scsi/scsi-disk.c
+++ b/hw/scsi/scsi-disk.c
@@ -775,11 +775,12 @@ int scsi_disk_emulate_vpd_page(SCSIRequest *req, uint8_t *outbuf)
}
case 0xb1: /* block device characteristics */
{
- buflen = 8;
+ buflen = 0x40;
outbuf[4] = (s->rotation_rate >> 8) & 0xff;
outbuf[5] = s->rotation_rate & 0xff;
- outbuf[6] = 0;
- outbuf[7] = 0;
+ outbuf[6] = 0; /* PRODUCT TYPE */
+ outbuf[7] = 0; /* WABEREQ | WACEREQ | NOMINAL FORM FACTOR */
+ outbuf[8] = 0; /* VBULS */
break;
}
case 0xb2: /* thin provisioning */
--
2.13.6
next prev parent reply other threads:[~2018-07-12 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 16:31 [Qemu-devel] [PULL 0/7] Block layer fixes for 3.0-rc1 Kevin Wolf
2018-07-12 16:31 ` [Qemu-devel] [PULL 1/7] iotests: 153: Fix dead code Kevin Wolf
2018-07-12 16:31 ` [Qemu-devel] [PULL 2/7] iotests: nbd: Stop qemu-nbd before remaking image Kevin Wolf
2018-07-12 16:31 ` [Qemu-devel] [PULL 3/7] qemu-img: Document copy offloading implications with -S and -c Kevin Wolf
2018-07-12 16:31 ` [Qemu-devel] [PULL 4/7] file-posix: specify expected filetypes Kevin Wolf
2018-07-12 16:31 ` [Qemu-devel] [PULL 5/7] iotests: add test 226 for file driver types Kevin Wolf
2018-07-12 16:31 ` Kevin Wolf [this message]
2018-07-12 16:31 ` [Qemu-devel] [PULL 7/7] qemu-img: align result of is_allocated_sectors Kevin Wolf
2018-07-12 17:24 ` [Qemu-devel] [PULL 0/7] Block layer fixes for 3.0-rc1 Peter Maydell
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=20180712163152.12521-7-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).