| commit | 27ce51df9a333ca7e05e09f6d25becf26ac1ff45 | |
| author | Dan Williams <dan.j.williams@intel.com> | |
| Thu, 3 Mar 2011 00:45:18 +0000 (2 16:45 -0800) | ||
| committer | Dan Williams <dan.j.williams@intel.com> | |
| Sun, 3 Jul 2011 10:55:29 +0000 (3 03:55 -0700) | ||
| tree | dbd50cc736c0eeb7e10ee2b15320c9f06b789f02 | treesnapshot (tar.gz zip) |
| parent | d7628d052242d634dc1e2584c422e690578918a3 | commitdiff |
isci: fix hang after target reset
When aborting a task context we need to be sure that the hardware has acted on
this request (retrieved the task context) before invalidating the remote node
context. In the case of the "dummy" task context and remote node we do not
have the full state machine that goes through the complete tc abort and rnc
invalidate states. Instead we ensure the hardware has seen and acted on
Signed-off-by: Jacek Danecki <Jacek.Danecki@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
When aborting a task context we need to be sure that the hardware has acted on
this request (retrieved the task context) before invalidating the remote node
context. In the case of the "dummy" task context and remote node we do not
have the full state machine that goes through the complete tc abort and rnc
invalidate states. Instead we ensure the hardware has seen and acted on
Signed-off-by: Jacek Danecki <Jacek.Danecki@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| drivers/scsi/isci/core/scic_sds_port.c | diffblobblamehistory |