| commit | ed5eb44d43c04727df9f73863ef276b75df24562 | |
| author | NeilBrown <neilb@suse.de> | |
| Sun, 8 Jan 2012 14:41:51 +0000 (9 01:41 +1100) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Wed, 18 Jan 2012 15:31:57 +0000 (18 07:31 -0800) | ||
| tree | b7ee47df17ea82ab4c3a5bb5b3e957c432e05847 | treesnapshot (tar.gz zip) |
| parent | efac38b1b6965dd9d16b3e2c91118e583b66e128 | commitdiff |
md/raid1: perform bad-block tests for WriteMostly devices too.
commit 307729c8bc5b5a41361af8af95906eee7552acb1 upstream.
We normally try to avoid reading from write-mostly devices, but when
we do we really have to check for bad blocks and be sure not to
try reading them.
With the current code, best_good_sectors might not get set and that
causes zero-length read requests to be send down which is very
confusing.
This bug was introduced in commit d2eb35acfdccbe2 and so the patch
is suitable for 3.1.x and 3.2.x
Reported-and-tested-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Reported-and-tested-by: Art -kwaak- van Breemen <ard@telegraafnet.nl>
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 307729c8bc5b5a41361af8af95906eee7552acb1 upstream.
We normally try to avoid reading from write-mostly devices, but when
we do we really have to check for bad blocks and be sure not to
try reading them.
With the current code, best_good_sectors might not get set and that
causes zero-length read requests to be send down which is very
confusing.
This bug was introduced in commit d2eb35acfdccbe2 and so the patch
is suitable for 3.1.x and 3.2.x
Reported-and-tested-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Reported-and-tested-by: Art -kwaak- van Breemen <ard@telegraafnet.nl>
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/md/raid1.c | diffblobblamehistory |