summaryrefslogtreecommitdiff
path: root/block/blk-timeout.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-12-01 06:30:59 (GMT)
committerNeilBrown <neilb@suse.de>2009-12-01 06:30:59 (GMT)
commitd0e260782c3702a009645c3caa02e381dab8798b (patch)
tree588f7776216df124d9372c7ced833b0bfb6d0a7f /block/blk-timeout.c
parenta9366e61b03f55a6e009e687ad10e706714c9907 (diff)
downloadlinux-d0e260782c3702a009645c3caa02e381dab8798b.tar.xz
md: revert incorrect fix for read error handling in raid1.
commit 4706b349f was a forward port of a fix that was needed for SLES10. But in fact it is not needed in mainline because the earlier commit dd00a99e7a fixes the same problem in a better way. Further, this commit introduces a bug in the way it interacts with the automatic read-error-correction. If, after a read error is successfully corrected, the same disk is chosen to re-read - the re-read won't be attempted but an error will be returned instead. After reverting that commit, there is the possibility that a read error on a read-only array (where read errors cannot be corrected as that requires a write) will repeatedly read the same device and continue to get an error. So in the "Array is readonly" case, fail the drive immediately on a read error. Signed-off-by: NeilBrown <neilb@suse.de> Cc: stable@kernel.org
Diffstat (limited to 'block/blk-timeout.c')
0 files changed, 0 insertions, 0 deletions