From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH/RFT] libata "DMA timeout" fix
Date: Sat, 28 Feb 2004 16:23:35 -0500 [thread overview]
Message-ID: <404106D7.8050809@pobox.com> (raw)
In-Reply-To: <1078001357.2020.90.camel@mulgrave>
James Bottomley wrote:
> On Sat, 2004-02-28 at 13:10, Jeff Garzik wrote:
>
>>===== drivers/scsi/libata-core.c 1.19 vs edited =====
>>--- 1.19/drivers/scsi/libata-core.c Wed Feb 25 22:41:13 2004
>>+++ edited/drivers/scsi/libata-core.c Sat Feb 28 14:03:18 2004
>>@@ -2130,6 +2130,14 @@
>> cmd->result = SAM_STAT_CHECK_CONDITION;
>> else
>> ata_to_sense_error(qc);
>>+
>>+ /* hack alert! we need this to get past the
>>+ * first check in scsi_done(). libata is the
>>+ * -only- user of ->eh_strategy_handler() in
>>+ * any kernel tree, which exposes some incorrect
>>+ * assumptions in the SCSI layer.
>>+ */
>>+ scsi_add_timer(cmd, 2000 * HZ, NULL);
>> } else {
>> cmd->result = SAM_STAT_GOOD;
>> }
>
>
> You can't do this. Supposing there command's delayed, the timer fires
> and then the command returns with a sense error? The done will go
> through automatically completing the command, but your strategy handler
> will still think it has a failed command to handle.
hmmm, yeah that will be a problem iff we are not already in the strategy
handler.
> The correct fix is this, I think (uncompiled, but you get the idea):
Yeah, that's much better. That function is not exported though ;-)
Jeff
next prev parent reply other threads:[~2004-02-28 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 19:10 [PATCH/RFT] libata "DMA timeout" fix Jeff Garzik
2004-02-28 20:49 ` James Bottomley
2004-02-28 21:23 ` Jeff Garzik [this message]
2004-02-28 21:28 ` James Bottomley
2004-02-29 17:26 ` Justin Cormack
2004-02-29 17:31 ` Jeff Garzik
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=404106D7.8050809@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.