public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ishai Rabinovitz <ishai@mellanox.co.il>
To: Erez Zilber <erezz@voltaire.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Receiving a SCSI response after abort task was sent
Date: Sun, 2 Jul 2006 16:22:31 +0300	[thread overview]
Message-ID: <20060702132231.GA10030@mellanox.co.il> (raw)
In-Reply-To: <44A7A547.6080709@voltaire.com>

On Sun, Jul 02, 2006 at 01:51:51PM +0300, Erez Zilber wrote:
> Hi,
> 
> I have a question about aborting tasks: when an initiator sends "abort 
> task" to the target, it is possible that the target will send a SCSI 
> response for the same task before receiving the abort task (I guess that 
> the target won't send a task management response for the abort task). 
> What should the initiator do with the SCSI response? Is the host that 
> issued the abort task willing to receive a SCSI response for that task? 
> Is it willing to receive only a task management response for the abort task?
> 
> This message was also sent to ips mailing list.
> 
> Thanks
> -- 
> 

In my opinion the initiator should work with the response and call the
done callback of this SCSI command.
This is the way we implement it in SRP: When we get a response for the task 
we set a bit indicting that this command was done. 
In the code that sends the task management and waits for response, we check 
after getting the response if this flag is set. If the flag is set we call 
the done callback. If it is not set, we set the result of the command to 
DID_ABORT.


-- 
Ishai Rabinovitz

  reply	other threads:[~2006-07-02 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02 10:51 Receiving a SCSI response after abort task was sent Erez Zilber
2006-07-02 13:22 ` Ishai Rabinovitz [this message]
2006-07-02 13:47   ` Erez Zilber
2006-07-02 15:14     ` Ishai Rabinovitz
2006-07-02 15:54 ` James Smart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060702132231.GA10030@mellanox.co.il \
    --to=ishai@mellanox.co.il \
    --cc=erezz@voltaire.com \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox