linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	hch@lst.de, James.Bottomley@SteelEye.com,
	alan@lxorguk.ukuu.org.uk, albertcc@tw.ibm.com,
	arjan@infradead.org, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] SCSI: implement scsi_eh_schedule_cmd()
Date: Wed, 12 Apr 2006 11:21:34 +0900	[thread overview]
Message-ID: <443C642E.5090106@gmail.com> (raw)
In-Reply-To: <20060411212830.GA9234@us.ibm.com>

Patrick Mansfield wrote:
> On Tue, Apr 11, 2006 at 01:41:57PM -0400, Jeff Garzik wrote:
>> Tejun Heo wrote:
>>> + * scsi_eh_schedule_cmd - schedule scsi cmd for error handling.
>>> + * @scmd:	scmd to run eh on.
>>> + *
>>> + * Description:
>>> + *	This function is used by LLDDs which don't use standard SCSI
>>> + *	EH to schedule scmd for EH.
>>> + *
>>> + * Return value:
>>> + *	0 on failure.
>>> + **/
>>> +int scsi_eh_schedule_cmd(struct scsi_cmnd *scmd)
[--snip--]
>>
>> ACK, though this patch makes me think that there are some non-libata 
>> pieces of code that could use this function.
>>
>> Unfortunately for libata, we are stuck waiting on linux-scsi people to 
>> return and give their opinion.  If nobody complains, I'll apply it, if 
>> it doesn't appear in scsi-misc-2.6 sometime vaguely soon.
> 
> Per other email it should be called scsi_req_abort_cmd() or such, as that
> is the only reason to call it, correct?

Well, it's named this way is to keep it consistent with 
scsi_eh_schedule_host().  Either name is okay with me but driver which 
use this function probably have interest in schedule_host() but not in 
other SCSI EH functions.  So, considering that, I think the current 
naming is okay.

> Any other handling can be completed by calling the ->done function.
> 
> Even the abort/cancel could be done in the driver without this, I assume
> it is avaiable so the driver can use the eh process and existing code
> paths rather than duplicate similar code.

Yeap, as I noted earlier, passing scmds to EH is possible without this 
function but it has to be done in a quite hackish way.  My earlier 
libata EH implementation did this by completing the scmd with CHECK 
CONDITION but without sense data which makes SCSI midlayer invoke EH to 
acquire sense data, at which point libata EH can take over and do EH. 
It's just ugly.  Again, I'm okay with whatever that works, but things 
are much simpler this way.

-- 
tejun

  reply	other threads:[~2006-04-12  2:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01 10:38 [PATCH] SCSI: implement scsi_eh_schedule() Tejun Heo
2006-04-01 20:14 ` Jeff Garzik
2006-04-02  1:15   ` Tejun Heo
2006-04-02 16:04     ` [PATCH 1/2] SCSI: implement scsi_eh_schedule_cmd() Tejun Heo
2006-04-02 16:06       ` [PATCH 2/2] SCSI: implement scsi_eh_schedule_host() Tejun Heo
2006-04-11 17:43         ` Jeff Garzik
2006-04-02 23:49       ` [PATCH 1/2] SCSI: implement scsi_eh_schedule_cmd() Luben Tuikov
2006-04-03  1:24         ` Tejun Heo
2006-04-11 17:41       ` Jeff Garzik
2006-04-11 21:28         ` Patrick Mansfield
2006-04-12  2:21           ` Tejun Heo [this message]
2006-04-12  8:24             ` Luben Tuikov
2006-04-12 16:18               ` Patrick Mansfield
2006-04-13  5:32                 ` Tejun Heo
2006-04-14  8:49                   ` Luben Tuikov
2006-04-14 12:02                     ` Tejun Heo
2006-04-19 18:49                       ` Luben Tuikov
2006-04-20  2:07                         ` Tejun Heo
2006-04-20 13:01                           ` Christoph Hellwig
2006-04-21  2:22                             ` Tejun Heo
2006-04-20 19:23                           ` Luben Tuikov
2006-04-21  2:39                             ` Tejun Heo

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=443C642E.5090106@gmail.com \
    --to=htejun@gmail.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=albertcc@tw.ibm.com \
    --cc=arjan@infradead.org \
    --cc=hch@lst.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.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;
as well as URLs for NNTP newsgroup(s).