tree 83ae95ce9a57d605ce2a308ceb2a026e9f2ca9b2
parent ba280c092e6eca8a70c502e4510061535fdce382
author Lars Ellenberg <lars.ellenberg@linbit.com> 1335364055 +0200
committer Philipp Reisner <philipp.reisner@linbit.com> 1336569419 +0200

drbd: fix race between drbdadm invalidate/verify and finishing resync

When a resync or online verify is finished or aborted,
drbd does a bulk write-out of changed bitmap pages.

If *in that very moment* a new verify or resync is triggered,
this can race:
 ASSERT( !test_bit(BITMAP_IO, &mdev->flags) ) in drbd_main.c
 FIXME going to queue 'set_n_write from StartingSync' but 'write from resync_finished' still pending?
and similar.

This can be observed with e.g. tight invalidate loops in test scripts,
and probably has no real-life implication.

Still, that race can be solved by first quiescen the device,
before starting a new resync or verify.

Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>