diff options
| author | Lars Ellenberg | 2012-06-19 10:27:58 +0200 |
|---|---|---|
| committer | Philipp Reisner | 2012-07-24 14:15:58 +0200 |
| commit | 7ee1fb93f390f7a7231abec4e34e6ab20abeed45 (patch) | |
| tree | 34a4e86335dc8f6dca13abcae3bf60ca5f8b37ab /drivers/block/drbd/drbd_main.c | |
| parent | drbd: fix potential access after free (diff) | |
| download | kernel-qcow2-linux-7ee1fb93f390f7a7231abec4e34e6ab20abeed45.tar.gz kernel-qcow2-linux-7ee1fb93f390f7a7231abec4e34e6ab20abeed45.tar.xz kernel-qcow2-linux-7ee1fb93f390f7a7231abec4e34e6ab20abeed45.zip | |
drbd: flush drbd work queue before invalidate/invalidate remote
If you do back to back wait-sync/invalidate on a Primary in a tight loop,
during application IO load, you could trigger a race:
kernel: block drbd6: FIXME going to queue 'set_n_write from StartingSync'
but 'write from resync_finished' still pending?
Fix this by changing the order of the drbd_queue_work() and
the wake_up() in dec_ap_pending(), and adding the additional
drbd_flush_workqueue() before requesting the full sync.
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
Diffstat (limited to 'drivers/block/drbd/drbd_main.c')
0 files changed, 0 insertions, 0 deletions