aboutsummaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2017-04-13 12:13:00 +1000
committerMartin K. Petersen <martin.petersen@oracle.com>2017-04-19 19:12:11 -0400
commit25d1d50e23275e141e3a3fe06c25a99f4c4bf4e0 (patch)
treeb22ddc5b4d4fd62a0286f53a2338e24f454277b0 /Makefile
parentscsi: lpfc: fix potential buffer overflow. (diff)
downloadlinux-dev-25d1d50e23275e141e3a3fe06c25a99f4c4bf4e0.tar.xz
linux-dev-25d1d50e23275e141e3a3fe06c25a99f4c4bf4e0.zip
scsi: virtio_scsi: Always try to read VPD pages
Passed through SCSI targets may have transfer limits which come from the host SCSI controller or something on the host side other than the target itself. To make this work properly, the hypervisor can adjust the target's VPD information to advertise these limits. But for that to work, the guest has to look at the VPD pages, which we won't do by default if it is an SPC-2 device, even if it does actually support it. This adds a workaround to address this, forcing devices attached to a virtio-scsi controller to always check the VPD pages. This is modelled on a similar workaround for the storvsc (Hyper-V) SCSI controller, although that exists for slightly different reasons. A specific case which causes this is a volume from IBM's IPR RAID controller (which presents as an SPC-2 device, although it does support VPD) passed through with qemu's 'scsi-block' device. [mkp: fixed typo] Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Acked-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions