From: Luben Tuikov <ltuikov@yahoo.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] SCSI: Introduce scsi_req_abort_cmd
Date: Tue, 31 Jan 2006 19:39:06 -0800 (PST) [thread overview]
Message-ID: <20060201033906.30216.qmail@web31811.mail.mud.yahoo.com> (raw)
In-Reply-To: <1138750263.3307.40.camel@mulgrave>
--- James Bottomley <James.Bottomley@SteelEye.com> wrote:
> On Thu, 2006-01-26 at 21:22 -0800, Luben Tuikov wrote:
> > Introduce scsi_req_abort_cmd(struct scsi_cmnd *).
> > This function requests that SCSI Core start recovery for the
> > command by deleting the timer and adding the command to the eh
> > queue. It can be called by either LLDDs or SCSI Core. LLDDs who
> > implement their own error recovery MAY ignore the timeout event if
> > they generated scsi_req_abort_cmd.
>
> In theory, the code to do this already exists: the current way to
> achieve this is supposed to be to return a status of DID_TIME_OUT to the
> command, which triggers error recovery. The only difference between
> this and what you propose is that the eh_timed_out API won't get called
> (presumably OK since the LLD already knows it wishes to trigger the
> error handler) and that the error handler will begin at the device reset
> task management function (again, on the assumption that the LLD cleaned
> everything up before returning DID_TIME_OUT). Is that sufficient for
> your purpose or do we really need another API?
No, it is not sufficient.
Yes, you really do need another API.
Luben
prev parent reply other threads:[~2006-02-01 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 5:22 [PATCH] SCSI: Introduce scsi_req_abort_cmd Luben Tuikov
2006-01-31 23:31 ` James Bottomley
2006-02-01 3:39 ` Luben Tuikov [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=20060201033906.30216.qmail@web31811.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=James.Bottomley@SteelEye.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