diff options
| author | NeilBrown <neilb@suse.de> | 2015-06-12 20:05:04 +1000 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2015-06-12 20:16:33 +1000 |
| commit | ea358cd0d2c634ff1379a1392edcdf2289f31e13 (patch) | |
| tree | 10c556b9ae108c35af563df9041e3d1948295e66 /tools/perf/scripts/python/futex-contention.py | |
| parent | 8e8e2518fceca407bb8fc2a6710d19d2e217892e (diff) | |
md: make sure MD_RECOVERY_DONE is clear before starting recovery/resync
MD_RECOVERY_DONE is normally cleared by md_check_recovery after a
resync etc finished. However it is possible for raid5_start_reshape
to race and start a reshape before MD_RECOVERY_DONE is cleared. This
can lean to multiple reshapes running at the same time, which isn't
good.
To make sure it is cleared before starting a reshape, and also clear
it when reaping a thread, just to be safe.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'tools/perf/scripts/python/futex-contention.py')
0 files changed, 0 insertions, 0 deletions