diff options
author | NeilBrown <neilb@suse.com> | 2015-07-27 11:48:52 +1000 |
---|---|---|
committer | NeilBrown <neilb@suse.com> | 2015-08-03 12:29:42 +1000 |
commit | 423f04d63cf421ea436bcc5be02543d549ce4b28 (patch) | |
tree | 0d98d3b3de62c7689fbe58a6229c7d760d998c55 /crypto | |
parent | 74d33293e467df61de1b1d8b2fbe29e550dec33b (diff) | |
download | lwn-423f04d63cf421ea436bcc5be02543d549ce4b28.tar.gz lwn-423f04d63cf421ea436bcc5be02543d549ce4b28.zip |
md/raid1: extend spinlock to protect raid1_end_read_request against inconsistencies
raid1_end_read_request() assumes that the In_sync bits are consistent
with the ->degaded count.
raid1_spare_active updates the In_sync bit before the ->degraded count
and so exposes an inconsistency, as does error()
So extend the spinlock in raid1_spare_active() and error() to hide those
inconsistencies.
This should probably be part of
Commit: 34cab6f42003 ("md/raid1: fix test for 'was read error from
last working device'.")
as it addresses the same issue. It fixes the same bug and should go
to -stable for same reasons.
Fixes: 76073054c95b ("md/raid1: clean up read_balance.")
Cc: stable@vger.kernel.org (v3.0+)
Signed-off-by: NeilBrown <neilb@suse.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions