summaryrefslogtreecommitdiffstats
path: root/drivers/md
diff options
context:
space:
mode:
authorShaohua Li <shli@fb.com>2015-05-29 02:33:47 +0200
committerNeilBrown <neilb@suse.de>2015-06-17 02:00:33 +0200
commit713bc5c2deb437ef40d48374ae6a57e030bd9e35 (patch)
treeff7c83d17990a4e910d29cda53c1c41d9c0b3e28 /drivers/md
parentmd/raid5: per hash value and exclusive wait_for_stripe (diff)
downloadlinux-713bc5c2deb437ef40d48374ae6a57e030bd9e35.tar.xz
linux-713bc5c2deb437ef40d48374ae6a57e030bd9e35.zip
md/raid5: ignore released_stripes check
conf->released_stripes list isn't always related to where there are free stripes pending. Active stripes can be in the list too. And even free stripes were active very recently. Signed-off-by: Shaohua Li <shli@fb.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md')
-rw-r--r--drivers/md/raid5.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 9a3b143b0b68..59e44e99eef3 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -681,8 +681,8 @@ get_active_stripe(struct r5conf *conf, sector_t sector,
if (!sh) {
if (!test_bit(R5_INACTIVE_BLOCKED, &conf->cache_state)) {
sh = get_free_stripe(conf, hash);
- if (!sh && llist_empty(&conf->released_stripes) &&
- !test_bit(R5_DID_ALLOC, &conf->cache_state))
+ if (!sh && !test_bit(R5_DID_ALLOC,
+ &conf->cache_state))
set_bit(R5_ALLOC_MORE,
&conf->cache_state);
}