public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: Luben Tuikov <luben@splentec.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Q: aborting commands
Date: Tue, 15 Oct 2002 17:20:07 -0700	[thread overview]
Message-ID: <20021016002007.GK1049@beaverton.ibm.com> (raw)
In-Reply-To: <3DACACAC.9AA42D85@splentec.com>

Luben Tuikov [luben@splentec.com] wrote:
> Mike Anderson wrote:
> > 
> > Luben Tuikov [luben@splentec.com] wrote:
> > > I've been meaning to ask this for some time now:
> > > What is the consensus on the meaning of an aborted command?
> > >
> > > Most notably in the SCSI LLP standards, a successfully aborted command
> > > will NOT return status as non-aborted commands would (normally) do.
> > >
> > > 1. Should successfully aborted commands call scsi_done()?
> > >    (of course with result=DID_ABORT)
> >
> > The new eh on calling eh_abort_handler on a cmd believes that it is the
> > owner of the command again.
> 
> Yes, we know. That's why the ability to sleep on eh, else
> there's no way out...

Ok so is the question should "all" io complete through scsi_done? 

When I looked at faster recovery of a timed out commands I was trying to
determine if it would be simpler for the abort io to call scsi_done. I
thought it would be because ownership would be cleaner.

It would also be good to start the abort ASAP on a timeout but the
context is wrong if the LLDD needs to sleep.

-andmike
--
Michael Anderson
andmike@us.ibm.com


      reply	other threads:[~2002-10-16  0:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 20:48 Q: aborting commands Luben Tuikov
2002-10-15 22:25 ` Mike Anderson
2002-10-16  0:02   ` Luben Tuikov
2002-10-16  0:20     ` Mike Anderson [this message]

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=20021016002007.GK1049@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=luben@splentec.com \
    /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