diff options
author | Stephen Hemminger <stephen@networkplumber.org> | 2017-03-07 09:15:53 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-12-16 10:33:50 +0100 |
commit | 696fbe191acd2809e2e8b385b455845cf0a18887 (patch) | |
tree | 32ef71fe6297155b419912dabb4c1cd29be02e81 /usr/Makefile | |
parent | dd8c78e2501eae30d27de93e6f17caf1504a3174 (diff) | |
download | linux-stable-696fbe191acd2809e2e8b385b455845cf0a18887.tar.gz linux-stable-696fbe191acd2809e2e8b385b455845cf0a18887.tar.bz2 linux-stable-696fbe191acd2809e2e8b385b455845cf0a18887.zip |
scsi: storvsc: Workaround for virtual DVD SCSI version
commit f1c635b439a5c01776fe3a25b1e2dc546ea82e6f upstream.
Hyper-V host emulation of SCSI for virtual DVD device reports SCSI
version 0 (UNKNOWN) but is still capable of supporting REPORTLUN.
Without this patch, a GEN2 Linux guest on Hyper-V will not boot 4.11
successfully with virtual DVD ROM device. What happens is that the SCSI
scan process falls back to doing sequential probing by INQUIRY. But the
storvsc driver has a previous workaround that masks/blocks all errors
reports from INQUIRY (or MODE_SENSE) commands. This workaround causes
the scan to then populate a full set of bogus LUN's on the target and
then sends kernel spinning off into a death spiral doing block reads on
the non-existent LUNs.
By setting the correct blacklist flags, the target with the DVD device
is scanned with REPORTLUN and that works correctly.
Patch needs to go in current 4.11, it is safe but not necessary in older
kernels.
Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
Reviewed-by: K. Y. Srinivasan <kys@microsoft.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'usr/Makefile')
0 files changed, 0 insertions, 0 deletions