From: Jeff Garzik <jgarzik@pobox.com>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Albert Lee <albertcc@tw.ibm.com>, Andy Warner <andyw@pobox.com>
Subject: libata todo item: retry certain classes of errors
Date: Thu, 06 Jan 2005 23:33:28 -0500 [thread overview]
Message-ID: <41DE1118.9020209@pobox.com> (raw)
libata error handling is still of the "stupid simple" variety. While
that makes it easy to verify, it also means that we don't always recover
from some situations.
Right now, libata simply returns an error back to the SCSI layer.
For DMA, PCI and SATA bus errors, we need to reset the hardware and
retry the command.
It's a fairly important project, for anyone ambitious. Error handling
must be improved before I implement queueing (and possibly hotplug).
Jeff
next reply other threads:[~2005-01-07 4:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 4:33 Jeff Garzik [this message]
2005-01-07 14:49 ` libata todo item: retry certain classes of errors Alan Cox
2005-02-02 1:50 ` Jeff Garzik
2005-02-03 10:02 ` Alan Cox
2005-02-03 17:24 ` Jeff Garzik
2005-02-03 17:16 ` Alan Cox
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=41DE1118.9020209@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=andyw@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 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).