aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-07-01 13:15:35 +1000
committerNeilBrown <neilb@suse.de>2009-07-01 13:15:35 +1000
commita5c308d4d1659b1f4833b863394e3e24cdbdfc6e (patch)
tree6affde6f3f03c01f651210cc042a07ba70533d03
parent0909dc448c98ed5021c87ffdfc09fb473aa464ab (diff)
downloadkernel_samsung_crespo-a5c308d4d1659b1f4833b863394e3e24cdbdfc6e.zip
kernel_samsung_crespo-a5c308d4d1659b1f4833b863394e3e24cdbdfc6e.tar.gz
kernel_samsung_crespo-a5c308d4d1659b1f4833b863394e3e24cdbdfc6e.tar.bz2
md/raid5: suspend shouldn't affect read requests.
md allows write to regions on an array to be suspended temporarily. This allows user-space to participate is aspects of reshape. In particular, data can be copied with not risk of a race. We should not be blocking read requests though, so don't. Cc: stable@kernel.org Signed-off-by: NeilBrown <neilb@suse.de>
-rw-r--r--drivers/md/raid5.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 92ef9b6..1f444ae 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -3702,7 +3702,8 @@ static int make_request(struct request_queue *q, struct bio * bi)
/* FIXME what if we get a false positive because these
* are being updated.
*/
- if (logical_sector >= mddev->suspend_lo &&
+ if (bio_data_dir(bi) == WRITE &&
+ logical_sector >= mddev->suspend_lo &&
logical_sector < mddev->suspend_hi) {
release_stripe(sh);
schedule();