diff options
author | NeilBrown <neilb@suse.de> | 2014-01-14 15:16:10 +1100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2014-01-14 16:44:07 +1100 |
commit | 5af9bef72c074dbe946da8b74eabd79cd5a9ff19 (patch) | |
tree | d2572106b3e41964a96dbf0fe71f4c22e486802d /drivers/md/raid10.c | |
parent | 41a336e011887f73e7c879b60e1e3544045435cb (diff) | |
download | linux-5af9bef72c074dbe946da8b74eabd79cd5a9ff19.tar.gz linux-5af9bef72c074dbe946da8b74eabd79cd5a9ff19.tar.bz2 linux-5af9bef72c074dbe946da8b74eabd79cd5a9ff19.zip |
md/raid5: fix a recently broken BUG_ON().
commit 6d183de4077191d1201283a9035ce57a9b05254d
md/raid5: fix newly-broken locking in get_active_stripe.
simplified a BUG_ON, but removed too much so now it sometimes fires
when it shouldn't.
When the STRIPE_EXPANDING flag is set, the stripe_head might be on a
special list while multiple stripe_heads are collected, or it might
not be on any list, even a 'free' list when the refcount is zero. As
long as STRIPE_EXPANDING is set, it will be found and added back to a
list eventually.
So both of the BUG_ONs which test for the ->lru being empty or not
need to avoid the case where STRIPE_EXPANDING is set.
The patch which broke this was marked for -stable, so this patch needs
to be applied to any branch that received 6d183de4
Fixes: 6d183de4077191d1201283a9035ce57a9b05254d
Cc: stable@vger.kernel.org (any release to which above was applied)
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid10.c')
0 files changed, 0 insertions, 0 deletions