diff options
| author |   Michael Kelley <mikelley@microsoft.com> | 2023-07-20 14:05:02 -0700 |
|---|---|---|
| committer |   Martin K. Petersen <martin.petersen@oracle.com> | 2023-07-23 15:43:15 -0400 |
| commit | 010c1e1c5741365dbbf44a5a5bb9f30192875c4c (patch) | |
| tree | cd81048f74854c1c36501fb6e9bcf59c11bd3e52 /scripts/generate_rust_analyzer.py | |
| parent | scsi: sg: Fix checking return value of blk_get_queue() (diff) | |
| download | linux-rng-010c1e1c5741365dbbf44a5a5bb9f30192875c4c.tar.xz linux-rng-010c1e1c5741365dbbf44a5a5bb9f30192875c4c.zip | |
scsi: storvsc: Limit max_sectors for virtual Fibre Channel devices
The Hyper-V host is queried to get the max transfer size that it supports,
and this value is used to set max_sectors for the synthetic SCSI
controller. However, this max transfer size may be too large for virtual
Fibre Channel devices, which are limited to 512 Kbytes. If a larger
transfer size is used with a vFC device, Hyper-V always returns an error,
and storvsc logs a message like this where the SRB status and SCSI status
are both zero:
hv_storvsc <GUID>: tag#197 cmd 0x8a status: scsi 0x0 srb 0x0 hv 0xc0000001
Add logic to limit the max transfer size to 512 Kbytes for vFC devices.
Fixes: 1d3e0980782f ("scsi: storvsc: Correct reporting of Hyper-V I/O size limits")
Cc: stable@vger.kernel.org
Signed-off-by: Michael Kelley <mikelley@microsoft.com>
Link: https://lore.kernel.org/r/1689887102-32806-1-git-send-email-mikelley@microsoft.com
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions