diff options
author | 2023-07-07 21:01:26 -0700 | |
---|---|---|
committer | 2023-07-11 12:38:49 -0400 | |
commit | f4d1a8e011909fee24643f84bd1196e1366c26f2 (patch) | |
tree | 93ddfc77a27d24aaa6db39cd4676b96a8793aaad /scripts/generate_rust_analyzer.py | |
parent | Merge branch '6.5/scsi-staging' into 6.5/scsi-fixes (diff) | |
download | linux-rng-f4d1a8e011909fee24643f84bd1196e1366c26f2.tar.xz linux-rng-f4d1a8e011909fee24643f84bd1196e1366c26f2.zip |
scsi: storvsc: Handle SRB status value 0x30
In response to a disk I/O request, Hyper-V has been observed to return SRB
status value 0x30. This indicates the request was not processed by Hyper-V
because low memory conditions on the host caused an internal error. The
0x30 status is not recognized by storvsc, so the I/O operation is not
flagged as an error. The request is treated as if it completed normally but
with zero data transferred, causing a flood of retries.
Add a definition for this SRB status value and handle it like other error
statuses from the Hyper-V host.
Signed-off-by: Michael Kelley <mikelley@microsoft.com>
Link: https://lore.kernel.org/r/1688788886-94279-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