summaryrefslogtreecommitdiffstats
path: root/drivers/md/dm-raid.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2012-01-09 01:41:51 +1100
committerNeilBrown <neilb@suse.de>2012-01-11 08:35:17 +1100
commit307729c8bc5b5a41361af8af95906eee7552acb1 (patch)
tree9b20fe9c898ee4de85b64a8e41c92123dae0b093 /drivers/md/dm-raid.c
parentf2a371c5e74dd5685ab47effa4ac7b23b1fdaae5 (diff)
downloadop-kernel-dev-307729c8bc5b5a41361af8af95906eee7552acb1.zip
op-kernel-dev-307729c8bc5b5a41361af8af95906eee7552acb1.tar.gz
md/raid1: perform bad-block tests for WriteMostly devices too.
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> Cc: stable@vger.kernel.org
Diffstat (limited to 'drivers/md/dm-raid.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud