Skip to content

Commit b8a9d66

Browse files
Roman GushchinNeilBrown
Roman Gushchin
authored and
NeilBrown
committed
md/raid5: fix locking in handle_stripe_clean_event()
After commit 566c09c ("raid5: relieve lock contention in get_active_stripe()") __find_stripe() is called under conf->hash_locks + hash. But handle_stripe_clean_event() calls remove_hash() under conf->device_lock. Under some cirscumstances the hash chain can be circuited, and we get an infinite loop with disabled interrupts and locked hash lock in __find_stripe(). This leads to hard lockup on multiple CPUs and following system crash. I was able to reproduce this behavior on raid6 over 6 ssd disks. The devices_handle_discard_safely option should be set to enable trim support. The following script was used: for i in `seq 1 32`; do dd if=/dev/zero of=large$i bs=10M count=100 & done neilb: original was against a 3.x kernel. I forward-ported to 4.3-rc. This verison is suitable for any kernel since Commit: 59fc630 ("RAID5: batch adjacent full stripe write") (v4.1+). I'll post a version for earlier kernels to stable. Signed-off-by: Roman Gushchin <klamm@yandex-team.ru> Fixes: 566c09c ("raid5: relieve lock contention in get_active_stripe()") Signed-off-by: NeilBrown <neilb@suse.com> Cc: Shaohua Li <shli@kernel.org> Cc: <stable@vger.kernel.org> # 3.13 - 4.2
1 parent 8bce6d3 commit b8a9d66

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

drivers/md/raid5.c

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3499,6 +3499,7 @@ static void handle_stripe_clean_event(struct r5conf *conf,
34993499
}
35003500
if (!discard_pending &&
35013501
test_bit(R5_Discard, &sh->dev[sh->pd_idx].flags)) {
3502+
int hash;
35023503
clear_bit(R5_Discard, &sh->dev[sh->pd_idx].flags);
35033504
clear_bit(R5_UPTODATE, &sh->dev[sh->pd_idx].flags);
35043505
if (sh->qd_idx >= 0) {
@@ -3512,16 +3513,17 @@ static void handle_stripe_clean_event(struct r5conf *conf,
35123513
* no updated data, so remove it from hash list and the stripe
35133514
* will be reinitialized
35143515
*/
3515-
spin_lock_irq(&conf->device_lock);
35163516
unhash:
3517+
hash = sh->hash_lock_index;
3518+
spin_lock_irq(conf->hash_locks + hash);
35173519
remove_hash(sh);
3520+
spin_unlock_irq(conf->hash_locks + hash);
35183521
if (head_sh->batch_head) {
35193522
sh = list_first_entry(&sh->batch_list,
35203523
struct stripe_head, batch_list);
35213524
if (sh != head_sh)
35223525
goto unhash;
35233526
}
3524-
spin_unlock_irq(&conf->device_lock);
35253527
sh = head_sh;
35263528

35273529
if (test_bit(STRIPE_SYNC_REQUESTED, &sh->state))

0 commit comments

Comments
 (0)