summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorYe Bin <yebin10@huawei.com>2025-02-17 10:16:28 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-03-07 18:25:28 +0100
commitb5038504da33f58768dfdd3cfe956299f3d87ff1 (patch)
treeb4d36f5ea07d16ca72ceb17c8d5dcf3907a256da /scripts
parent40432672eb6f1d18ff37c1d80a8f77bd665df291 (diff)
downloadlinux-b5038504da33f58768dfdd3cfe956299f3d87ff1.tar.gz
linux-b5038504da33f58768dfdd3cfe956299f3d87ff1.tar.bz2
linux-b5038504da33f58768dfdd3cfe956299f3d87ff1.zip
scsi: core: Clear driver private data when retrying request
[ Upstream commit dce5c4afd035e8090a26e5d776b1682c0e649683 ] After commit 1bad6c4a57ef ("scsi: zero per-cmd private driver data for each MQ I/O"), the xen-scsifront/virtio_scsi/snic drivers all removed code that explicitly zeroed driver-private command data. In combination with commit 464a00c9e0ad ("scsi: core: Kill DRIVER_SENSE"), after virtio_scsi performs a capacity expansion, the first request will return a unit attention to indicate that the capacity has changed. And then the original command is retried. As driver-private command data was not cleared, the request would return UA again and eventually time out and fail. Zero driver-private command data when a request is retried. Fixes: f7de50da1479 ("scsi: xen-scsifront: Remove code that zeroes driver-private command data") Fixes: c2bb87318baa ("scsi: virtio_scsi: Remove code that zeroes driver-private command data") Fixes: c3006a926468 ("scsi: snic: Remove code that zeroes driver-private command data") Signed-off-by: Ye Bin <yebin10@huawei.com> Reviewed-by: Bart Van Assche <bvanassche@acm.org> Link: https://lore.kernel.org/r/20250217021628.2929248-1-yebin@huaweicloud.com Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions