diff options
| author | Alan Stern <[email protected]> | 2014-03-28 10:51:15 -0700 |
|---|---|---|
| committer | James Bottomley <[email protected]> | 2014-04-21 14:27:26 -0700 |
| commit | 644373a4219add42123df69c8b7ce6a918475ccd (patch) | |
| tree | bdf8825070f03d622ff3fa715f3ad5f19513bb4f /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | d555a2abf3481f81303d835046a5ec2c4fb3ca8e (diff) | |
[SCSI] Fix command result state propagation
We're seeing a case where the contents of scmd->result isn't being reset after
a SCSI command encounters an error, is resubmitted, times out and then gets
handled. The error handler acts on the stale result of the previous error
instead of the timeout. Fix this by properly zeroing the scmd->status before
the command is resubmitted.
Signed-off-by: Alan Stern <[email protected]>
Signed-off-by: James Bottomley <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions