qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, jcody@redhat.com, armbru@redhat.com,
	mreitz@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
	amit.shah@redhat.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH v5 13/13] block/mirror: Block "device IO" during mirror exit
Date: Wed, 20 May 2015 14:16:16 +0800	[thread overview]
Message-ID: <1432102576-6637-14-git-send-email-famz@redhat.com> (raw)
In-Reply-To: <1432102576-6637-1-git-send-email-famz@redhat.com>

When mirror should complete, the source and target are in sync.  But we
call bdrv_swap() only a while later in the main loop bh. If the guest
writes something before that, target will not get the new data.

Block "device IO" before bdrv_drain and unblock it after bdrw_swap().

Reported-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
---
 block/mirror.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/block/mirror.c b/block/mirror.c
index 58f391a..f400456 100644
--- a/block/mirror.c
+++ b/block/mirror.c
@@ -320,6 +320,8 @@ static void mirror_drain(MirrorBlockJob *s)
 
 typedef struct {
     int ret;
+    /* Use to pause device IO during mirror exit */
+    Error *blocker;
 } MirrorExitData;
 
 static void mirror_exit(BlockJob *job, void *opaque)
@@ -328,6 +330,8 @@ static void mirror_exit(BlockJob *job, void *opaque)
     MirrorExitData *data = opaque;
     AioContext *replace_aio_context = NULL;
 
+    bdrv_op_unblock(s->common.bs, BLOCK_OP_TYPE_DEVICE_IO, data->blocker);
+    error_free(data->blocker);
     if (s->to_replace) {
         replace_aio_context = bdrv_get_aio_context(s->to_replace);
         aio_context_acquire(replace_aio_context);
@@ -376,6 +380,8 @@ static void coroutine_fn mirror_run(void *opaque)
                                  checking for a NULL string */
     int ret = 0;
     int n;
+    data = g_malloc0(sizeof(*data));
+    error_setg(&data->blocker, "mirror job exiting");
 
     if (block_job_is_cancelled(&s->common)) {
         goto immediate_exit;
@@ -521,6 +527,7 @@ static void coroutine_fn mirror_run(void *opaque)
              * mirror_populate runs.
              */
             trace_mirror_before_drain(s, cnt);
+            bdrv_op_block(bs, BLOCK_OP_TYPE_DEVICE_IO, data->blocker);
             bdrv_drain(bs);
             cnt = bdrv_get_dirty_count(s->dirty_bitmap);
         }
@@ -543,6 +550,7 @@ static void coroutine_fn mirror_run(void *opaque)
             s->common.cancelled = false;
             break;
         }
+        bdrv_op_unblock(bs, BLOCK_OP_TYPE_DEVICE_IO, data->blocker);
         last_pause_ns = qemu_clock_get_ns(QEMU_CLOCK_REALTIME);
     }
 
@@ -563,7 +571,6 @@ immediate_exit:
     bdrv_release_dirty_bitmap(bs, s->dirty_bitmap);
     bdrv_iostatus_disable(s->target);
 
-    data = g_malloc(sizeof(*data));
     data->ret = ret;
     block_job_defer_to_main_loop(&s->common, mirror_exit, data);
 }
-- 
2.4.1

  parent reply	other threads:[~2015-05-20  6:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  6:16 [Qemu-devel] [PATCH v5 00/13] Fix transactional snapshot with dataplane and NBD export Fam Zheng
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 01/13] block: Add op blocker type "device IO" Fam Zheng
2015-05-23 15:20   ` Max Reitz
2015-05-23 15:25   ` Max Reitz
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 02/13] block: Add op blocker notifier list Fam Zheng
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 03/13] block-backend: Add blk_op_blocker_add_notifier Fam Zheng
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 04/13] virtio-blk: Move complete_request to 'ops' structure Fam Zheng
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 05/13] virtio-blk: Don't handle output when there is "device IO" op blocker Fam Zheng
2015-05-23 15:27   ` Max Reitz
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 06/13] virtio-scsi-dataplane: Add "device IO" op blocker listener Fam Zheng
2015-05-23 16:13   ` Max Reitz
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 07/13] nbd-server: Clear "can_read" when "device io" blocker is set Fam Zheng
2015-05-23 16:14   ` Max Reitz
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 08/13] blockdev: Block device IO during internal snapshot transaction Fam Zheng
2015-05-23 16:39   ` Max Reitz
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 09/13] blockdev: Block device IO during external " Fam Zheng
2015-05-23 16:43   ` Max Reitz
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 10/13] blockdev: Block device IO during drive-backup transaction Fam Zheng
2015-05-23 16:47   ` Max Reitz
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 11/13] blockdev: Block device IO during blockdev-backup transaction Fam Zheng
2015-05-20  6:16 ` [Qemu-devel] [PATCH v5 12/13] block: Block "device IO" during bdrv_drain and bdrv_drain_all Fam Zheng
2015-05-20  6:16 ` Fam Zheng [this message]
2015-05-20  6:32   ` [Qemu-devel] [PATCH v5 13/13] block/mirror: Block "device IO" during mirror exit Paolo Bonzini
2015-05-20  6:43     ` Fam Zheng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1432102576-6637-14-git-send-email-famz@redhat.com \
    --to=famz@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).