From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, linux-ide@vger.kernel.org, htejun@gmail.com
Subject: [PATCHSET] libata: improve media error handling
Date: Tue, 14 Nov 2006 22:47:09 +0900 [thread overview]
Message-ID: <1163512029469-git-send-email-htejun@gmail.com> (raw)
In-Reply-To:
Hello, Jeff.
This patchset improves media error handling. The problem is that ATA
devices transfer "indeterminate" amount of data on device error making
handling media errors difficult for highlevel driver to handle. The
current high level driver, sd, assumes that data upto the first failed
block has been transferred successfully, so data corruption is
possible.
This patchset makes libata-eh perform IO upto the first failed block
and report the first failed block to highlevel driver iff the partial
transfer was successful. Note that after this patchset LLDs using old
EH don't report the first failed block to high level. It wasn't safe
to begin with and no libata driver properly reported the first failed
sector before improve-sense-data-generation patchset anyway.
With this patchset applied, libata media error handling is well
integrated with sd.
This patchset is against
upstream(cfd15b0011498986ef14b6c53f5eaba89d2171f3)
+ improve-sense-data-generation patchset[1]
Thanks.
--
tejun
[1] http://thread.gmane.org/gmane.linux.ide/14035/focus=14035
next reply other threads:[~2006-11-14 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 13:47 Tejun Heo [this message]
2006-11-14 13:47 ` [PATCH 1/4] libata: implement ata_exec_internal_sg() Tejun Heo
2006-11-28 9:02 ` Jeff Garzik
2006-11-14 13:47 ` [PATCH 4/4] libata: improve media error handling Tejun Heo
2007-03-02 23:37 ` Jeff Garzik
2006-11-14 13:47 ` [PATCH 3/4] libata: prepare ata_sg_clean() for invocation from EH Tejun Heo
2006-11-28 9:02 ` Jeff Garzik
2006-11-14 13:47 ` [PATCH 2/4] libata: separate out rw ATA taskfile building into ata_build_tf() Tejun Heo
2006-11-14 16:13 ` Mark Lord
2006-11-14 16:51 ` Tejun Heo
2006-11-14 21:04 ` Mark Lord
2006-11-28 9:17 ` 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=1163512029469-git-send-email-htejun@gmail.com \
--to=htejun@gmail.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 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).