storvsc: port a Linux patch, properly set residual data length on errors

This change is based on Linux commit 40630f462824ee.  csio.resid should
account for transfer_len only for success and SRB_STATUS_DATA_OVERRUN
condition.

I am not sure how exactly this change works, but I have a report from a
user that they see lots of checksum errors when running a pool scrub
concurrently with iozone -l 1 -s 100G.  After applying this patch the
problem cannot be reproduced.

Reviewed by:	nobody
Sponsored by:	CyberSecure
Differential Revision: https://reviews.freebsd.org/D22312
This commit is contained in:
Andriy Gapon 2020-01-14 13:20:16 +00:00
parent 9c6eb0f92f
commit efdba95d62
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=356730
2 changed files with 7 additions and 2 deletions

View File

@ -2278,7 +2278,11 @@ storvsc_io_done(struct hv_storvsc_request *reqp)
}
ccb->csio.scsi_status = (vm_srb->scsi_status & 0xFF);
ccb->csio.resid = ccb->csio.dxfer_len - vm_srb->transfer_len;
if (srb_status == SRB_STATUS_SUCCESS ||
srb_status == SRB_STATUS_DATA_OVERRUN)
ccb->csio.resid = ccb->csio.dxfer_len - vm_srb->transfer_len;
else
ccb->csio.resid = ccb->csio.dxfer_len;
if (reqp->sense_info_len != 0) {
csio->sense_resid = csio->sense_len - reqp->sense_info_len;

View File

@ -245,7 +245,8 @@ struct vstor_packet {
#define SRB_STATUS_SUCCESS 0x01
#define SRB_STATUS_ABORTED 0x02
#define SRB_STATUS_ERROR 0x04
#define SRB_STATUS_INVALID_LUN 0x20
#define SRB_STATUS_DATA_OVERRUN 0x12
#define SRB_STATUS_INVALID_LUN 0x20
/**
* SRB Status Masks (can be combined with above status codes)
*/