linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Douglas Gilbert <dougg@torque.net>
Subject: Re: [PATCH] ATAPI error handling work
Date: Sat, 29 Oct 2005 14:33:23 -0400	[thread overview]
Message-ID: <4363C073.8020904@pobox.com> (raw)
In-Reply-To: <43453B2B.30405@gmail.com>

Tejun Heo wrote:
>  As I wrote in the libata EH doc and associated thread, I don't think 
> doing autosensing-by-turning-qc-around is a very good idea.  I hope I 
> can make some point here.

I like autosensing, particularly because we want to get away from using 
a lot of SCSI EH infrastructure, since libata will eventually be 
separated from SCSI.


>  In the other thread, you wrote that the current ATAPI sense requisition 
> is corrupt because it finishes scmd twice and I believe this patch was 
> implemented to fix that.  I disagreed with you in that thread and gave 
> my rationale for that.  If I was wrong in that thread, please ignore 
> what follows.

I correct myself:  the corruption occurs because we obtain the scsi host 
lock (our host_set lock), and then call scsi_finish_command().  This is 
in error, because scsi_finish_command() also acquires the scsi host lock 
via a call to scsi_device_unbusy().

Multiple possible solutions:  separate scsi host lock from our own. 
batching commands until the end of EH, as SCSI EH does.  continue work 
on auto-sensing.  ...

	Jeff



      reply	other threads:[~2005-10-29 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 20:51 [PATCH] ATAPI error handling work Jeff Garzik
2005-10-06  5:35 ` Tejun Heo
2005-10-06 10:09   ` Jeff Garzik
2005-10-06 14:56     ` Tejun Heo
2005-10-29 18:33       ` Jeff Garzik [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=4363C073.8020904@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=dougg@torque.net \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).