From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, linux-ide@vger.kernel.org, albertcc@tw.ibm.com
Cc: Tejun Heo <htejun@gmail.com>
Subject: [PATCH 3/4] libata: fix handling of race between timeout and completion
Date: Thu, 2 Feb 2006 00:56:10 +0900 [thread overview]
Message-ID: <11388093703309-git-send-email-htejun@gmail.com> (raw)
In-Reply-To: <11388093703495-git-send-email-htejun@gmail.com>
If a qc completes after SCSI timer expires but before libata EH kicks
in, the qc gets completed but the scsicmd still gets passed to libata
EH resulting in ->eng_timeout invocation with NULL qc. Currently none
of ->eng_timeout callbacks handles this properly. This patch makes
ata_scsi_error() bypass ->eng_timeout and handle this rare case.
Signed-off-by: Tejun Heo <htejun@gmail.com>
---
drivers/scsi/libata-scsi.c | 39 ++++++++++++++++++++++++++++++++++++---
1 files changed, 36 insertions(+), 3 deletions(-)
22f1716710352b49e5a1598b0c4efdebfa33014b
diff --git a/drivers/scsi/libata-scsi.c b/drivers/scsi/libata-scsi.c
index 0e14259..9435645 100644
--- a/drivers/scsi/libata-scsi.c
+++ b/drivers/scsi/libata-scsi.c
@@ -731,17 +731,50 @@ int ata_scsi_slave_config(struct scsi_de
int ata_scsi_error(struct Scsi_Host *host)
{
- struct ata_port *ap;
+ struct ata_port *ap = (struct ata_port *) &host->hostdata[0];
+ struct ata_queued_cmd *qc;
+ unsigned long flags;
DPRINTK("ENTER\n");
spin_lock_irqsave(&ap->host_set->lock, flags);
+ qc = ata_qc_from_tag(ap, ap->active_tag);
assert(!(ap->flags & ATA_FLAG_IN_EH));
ap->flags |= ATA_FLAG_IN_EH;
spin_unlock_irqrestore(&ap->host_set->lock, flags);
- ap = (struct ata_port *) &host->hostdata[0];
- ap->ops->eng_timeout(ap);
+ if (qc) {
+ ap->ops->eng_timeout(ap);
+ } else {
+ struct scsi_cmnd *scmd;
+ unsigned char *sb;
+
+ /* The scmd had timed out but the corresponding qc
+ * completed successfully inbetween timer expiration
+ * and here. Retry if possible.
+ *
+ * It is better to enter eng_timeout and perform EH
+ * before retrying the command, but this case should
+ * be _very_ rare and eng_timeout isn't ready for
+ * NULL-qc case.
+ */
+ scmd = list_entry(host->eh_cmd_q.next,
+ struct scsi_cmnd, eh_entry);
+ sb = scmd->sense_buffer;
+
+ /* Timeout, fake parity for now */
+ scmd->result = (DRIVER_SENSE << 24) | SAM_STAT_CHECK_CONDITION;
+ sb[0] = 0x70;
+ sb[7] = 0x0a;
+ sb[2] = ABORTED_COMMAND;
+ sb[12] = 0x47;
+ sb[13] = 0x00;
+
+ printk(KERN_WARNING "ata%u: interrupt and timer raced for "
+ "scsicmd %p\n", ap->id, scmd);
+
+ scsi_eh_finish_cmd(scmd, &ap->eh_done_q);
+ }
assert(host->host_failed == 0 && list_empty(&host->eh_cmd_q));
--
1.1.3
next prev parent reply other threads:[~2006-02-01 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 15:56 [PATCHSET] libata: various fixes related to EH, take #3 Tejun Heo
2006-02-01 15:56 ` [PATCH 1/4] libata: implement ATA_FLAG_IN_EH port flag Tejun Heo
2006-02-09 6:18 ` Jeff Garzik
2006-02-01 15:56 ` [PATCH 4/4] libata: kill NULL qc handling from ->eng_timeout callbacks Tejun Heo
2006-02-09 6:33 ` Jeff Garzik
2006-02-01 15:56 ` [PATCH 2/4] libata: EH / pio tasks synchronization Tejun Heo
2006-02-01 15:56 ` Tejun Heo [this message]
2006-02-09 6:33 ` [PATCH 3/4] libata: fix handling of race between timeout and completion Jeff Garzik
2006-02-09 9:08 ` Tejun
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=11388093703309-git-send-email-htejun@gmail.com \
--to=htejun@gmail.com \
--cc=albertcc@tw.ibm.com \
--cc=jgarzik@pobox.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 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.