summaryrefslogtreecommitdiff
path: root/arch/cris/arch-v10
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.com>2015-07-27 11:48:52 +1000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-08-16 20:51:41 -0700
commitc4a6d3f3491a55269ee1e8d99f6fa7bab15cc011 (patch)
treef30f1b0ee2d80bbd53391c32d10643f47474e174 /arch/cris/arch-v10
parent2a4cb7b52d728b1f6b76e73ea0277f422da1ffac (diff)
downloadlwn-c4a6d3f3491a55269ee1e8d99f6fa7bab15cc011.tar.gz
lwn-c4a6d3f3491a55269ee1e8d99f6fa7bab15cc011.zip
md/raid1: extend spinlock to protect raid1_end_read_request against inconsistencies
commit 423f04d63cf421ea436bcc5be02543d549ce4b28 upstream. 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.") Signed-off-by: NeilBrown <neilb@suse.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/cris/arch-v10')
0 files changed, 0 insertions, 0 deletions