Public bug reported:
Over last week we have made changes and fix bugs in storvsc , please include these patch set . [PATCH V3 1/7] Drivers: scsi: storvsc: Change the limits to reflect the values on the host In Hyper-V, each port/path/target maps to 1 scsi host adapter. In reality, the path/target is not used (ie always set to 0) so our scsi host adapter essentially has 1 bus with 1 target that contains up to 256 luns. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=01a1fc6a17a33edc6b43aca255b31f51497e2414 [PATCH V3 2/7] Drivers: scsi: storvsc: Set cmd_per_lun to reflect value supported by the Host Set cmd_per_lun to reflect value supported by the Host. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=4a1e22529bda70eacde631bf4611b61b7aac9ae6 [PATCH V3 3/7] Drivers: scsi: storvsc: Filter commands based on the storage protocol version Going forward it is possible that some of the commands that are not currently implemented will be implemented on future Windows hosts. Even if they are not implemented, we are told the host will corrrectly handle unsupported commands (by returning appropriate return code and sense information). Make command filtering depend on the host version. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=5aacedc1953dcaa1434a179147861319c919503e [PATCH V3 4/7] Drivers: scsi: storvsc: Fix a bug in handling VMBUS protocol version Based on the negotiated VMBUS protocol version, we adjust the size of the storage protocol messages. The two sizes we currently handle are pre-win8 and post-win8. In WS2012 R2, we are negotiating higher VMBUS protocol version than the win8 version. Make adjustments to correctly handle this. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=0d0da066835a1194f3a6c425054db90b089e74ea [PATCH 5/7] Drivers: scsi: storvsc: Implement a timedout handler On Azure, we have seen instances of unbounded I/O latencies. To deal with this issue, implement handler that can reset the timeout. Note that the host gaurantees that it will respond to each command that has been issued. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=ec5dafb2361fb393e12745bda837707be2041436 [PATCH 6/7] drivers: scsi: storvsc: Set srb_flags in all cases Correctly set SRB flags for all valid I/O directions. Some IHV drivers on the Windows host require this. The host validates the command and SRB flags prior to passing the command down to native driver stack. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=20e9f28dd87e62d10f2c434396c734da43329c57 [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. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=27ac92916691eab6c9ca74db19a4b13084d5c78d Thanks, Abhishek ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347169 Title: Various storvsc bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1347169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
