tree c0d082333a84c70b3eda3e68232eea88bbc52f39
parent 235549605eb7f1c5a37cef8b09d12e6d412c5cd6
author NeilBrown <neilb@suse.de> 1410328884 +1000
committer NeilBrown <neilb@suse.de> 1411349161 +1000

md/raid1: update next_resync under resync_lock.

raise_barrier() uses next_resync as part of its calculations, so it
really should be updated first, instead of afterwards.

next_resync is always used under resync_lock so update it under
resync lock to, just before it is used.  That is safest.

This could cause normal IO and resync IO to interact badly so
it suitable for -stable.

Fixes: 79ef3a8aa1cb1523cc231c9a90a278333c21f761
cc: stable@vger.kernel.org (v3.13+)
Signed-off-by: NeilBrown <neilb@suse.de>