diff options
| author | Lars Ellenberg <[email protected]> | 2012-04-25 16:27:35 +0200 |
|---|---|---|
| committer | Philipp Reisner <[email protected]> | 2012-05-09 15:16:59 +0200 |
| commit | a574daf5d722f4ca8cc18509f30b804c4d519962 (patch) | |
| tree | 83ae95ce9a57d605ce2a308ceb2a026e9f2ca9b2 /tools/perf/util/scripting-engines/trace-event-perl.c | |
| parent | ba280c092e6eca8a70c502e4510061535fdce382 (diff) | |
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 <[email protected]>
Signed-off-by: Lars Ellenberg <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-perl.c')
0 files changed, 0 insertions, 0 deletions