diff options
| author | NeilBrown <neilb@suse.com> | 2015-07-27 11:48:52 +1000 |
|---|---|---|
| committer | Zefan Li <lizefan@huawei.com> | 2016-03-21 09:17:50 +0800 |
| commit | 2411ca5d7a8f95646ba50962d20e06d9aa07a408 (patch) | |
| tree | 566b5e03a2f7c57f1a5d861d493c48b1c2a9ceef /net/unix/af_unix.c | |
| parent | 0444d9dfacb4fa42005ca3afefe56b16f07c5192 (diff) | |
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>
[lizf: Backported to 3.4: adjust context]
Signed-off-by: Zefan Li <lizefan@huawei.com>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions