IB/iser: Handle aborting a command after it is sent
authorErez Zilber <erezz@voltaire.com>
Sun, 25 Mar 2007 10:07:10 +0000 (12:07 +0200)
committerRoland Dreier <rolandd@cisco.com>
Mon, 26 Mar 2007 23:35:09 +0000 (16:35 -0700)
commit3104a2175dc04b7a597acea90f19b033abcfc7d8
treeeb98df79a13ae9f1fba08f349fa459f514a1b2dc
parent0264d8853137a9a328d9f0ed29e083dd505512cb
IB/iser: Handle aborting a command after it is sent

The SCSI midlayer may abort a command that was already sent.  If the
initiator is still trying to send the command (or data-out PDUs for
that command), the QP may time out after the midlayer times
out. Therefore, when aborting the command, iSER may still have
references for the command's buffers.  When sending these PDUs, the
sends will complete with an error and their resources will be released
then.

Signed-off-by: Erez Zilber <erezz@voltaire.com>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
drivers/infiniband/ulp/iser/iser_initiator.c