summaryrefslogtreecommitdiff
path: root/arch/m32r
diff options
context:
space:
mode:
authorWei Fang <fangwei1@huawei.com>2016-12-13 01:25:21 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-01-09 07:32:21 (GMT)
commit9d33a399566771b023a08f490344b70a200c87da (patch)
tree62f375fd028de4dff5f95093d0f1364d278a500c /arch/m32r
parent2a940b853ef679cd981e38f23c756d4335a3375c (diff)
downloadlinux-9d33a399566771b023a08f490344b70a200c87da.tar.xz
scsi: avoid a permanent stop of the scsi device's request queue
commit d2a145252c52792bc59e4767b486b26c430af4bb upstream. A race between scanning and fc_remote_port_delete() may result in a permanent stop if the device gets blocked before scsi_sysfs_add_sdev() and unblocked after. The reason is that blocking a device sets both the SDEV_BLOCKED state and the QUEUE_FLAG_STOPPED. However, scsi_sysfs_add_sdev() unconditionally sets SDEV_RUNNING which causes the device to be ignored by scsi_target_unblock() and thus never have its QUEUE_FLAG_STOPPED cleared leading to a device which is apparently running but has a stopped queue. We actually have two places where SDEV_RUNNING is set: once in scsi_add_lun() which respects the blocked flag and once in scsi_sysfs_add_sdev() which doesn't. Since the second set is entirely spurious, simply remove it to fix the problem. Reported-by: Zengxi Chen <chenzengxi@huawei.com> Signed-off-by: Wei Fang <fangwei1@huawei.com> Reviewed-by: Ewan D. Milne <emilne@redhat.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/m32r')
0 files changed, 0 insertions, 0 deletions