diff options
author | Michal Hocko <[email protected]> | 2015-08-27 20:16:37 +0200 |
---|---|---|
committer | James Bottomley <[email protected]> | 2015-09-06 12:05:45 -0700 |
commit | 537b604c8b3aa8b96fe35f87dd085816552e294c (patch) | |
tree | 62d373c3c0b74bfc2c317598edc59acb3daf28c6 /tools/perf/scripts/python | |
parent | 420fa2118c020a005e9f0311c1e0b27414306618 (diff) |
scsi: fix scsi_error_handler vs. scsi_host_dev_release race
b9d5c6b7ef57 ("[SCSI] cleanup setting task state in
scsi_error_handler()") has introduced a race between scsi_error_handler
and scsi_host_dev_release resulting in the hang when the device goes
away because scsi_error_handler might miss a wake up:
CPU0 CPU1
scsi_error_handler scsi_host_dev_release
kthread_stop()
kthread_should_stop()
test_bit(KTHREAD_SHOULD_STOP)
set_bit(KTHREAD_SHOULD_STOP)
wake_up_process()
wait_for_completion()
set_current_state(TASK_INTERRUPTIBLE)
schedule()
The most straightforward solution seems to be to invert the ordering of
the set_current_state and kthread_should_stop.
The issue has been noticed during reboot test on a 3.0 based kernel but
the current code seems to be affected in the same way.
[jejb: additional comment added]
Cc: <[email protected]> # 3.6+
Reported-and-debugged-by: Mike Mayer <[email protected]>
Signed-off-by: Michal Hocko <[email protected]>
Reviewed-by: Dan Williams <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Signed-off-by: James Bottomley <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions