lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <1405183712-23967-7-git-send-email-kys@microsoft.com> Date: Sat, 12 Jul 2014 09:48:32 -0700 From: "K. Y. Srinivasan" <kys@...rosoft.com> To: jasowang@...hat.com, apw@...onical.com, linux-kernel@...r.kernel.org, devel@...uxdriverproject.org, ohering@...e.com, jbottomley@...allels.com, hch@...radead.org, linux-scsi@...r.kernel.org Cc: "K. Y. Srinivasan" <kys@...rosoft.com>, <stable@...r.kernel.org> Subject: [PATCH 7/7] drivers: scsi: storvsc: Correctly handle TEST_UNIT_READY failure On some Windows hosts on FC SANs, TEST_UNIT_READY can return SRB_STATUS_ERROR. Correctly handle this. Note that there is sufficient sense information to support scsi error handling even in this case. In this version of the patch I have addressed comments from Christoph Hellwig <hch@...radead.org> Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com> Cc: <stable@...r.kernel.org> --- drivers/scsi/storvsc_drv.c | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c index 9342ba4..29d0329 100644 --- a/drivers/scsi/storvsc_drv.c +++ b/drivers/scsi/storvsc_drv.c @@ -1018,6 +1018,13 @@ static void storvsc_handle_error(struct vmscsi_request *vm_srb, case ATA_12: set_host_byte(scmnd, DID_PASSTHROUGH); break; + /* + * On Some Windows hosts TEST_UNIT_READY command can return + * SRB_STATUS_ERROR, let the upper level code deal with it + * based on the sense information. + */ + case TEST_UNIT_READY: + break; default: set_host_byte(scmnd, DID_TARGET_FAILURE); } -- 1.7.4.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists