From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Juan Quintela <quintela@redhat.com>,
mreitz@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 13/13] block/mirror: Block "device IO" during mirror exit
Date: Tue, 19 May 2015 10:04:51 +0200 [thread overview]
Message-ID: <555AEEA3.4080407@redhat.com> (raw)
In-Reply-To: <1432036186-29903-14-git-send-email-famz@redhat.com>
On 19/05/2015 13:49, Fam Zheng wrote:
> When block job mirror is finished, the source and target is synced. But
> we call bdrv_swap() later in main loop bh. If the guest write before
> that, target will not get the new data.
This is too late. As a rule, the blocker must be established before
calling bdrv_drain, and removed on the next yield (in this case, before
the assignment to last_pause_ns).
Paolo
> Reported-by: Wen Congyang <wency@cn.fujitsu.com>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block/mirror.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/block/mirror.c b/block/mirror.c
> index 58f391a..d96403b 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);
> @@ -563,8 +567,10 @@ immediate_exit:
> bdrv_release_dirty_bitmap(bs, s->dirty_bitmap);
> bdrv_iostatus_disable(s->target);
>
> - data = g_malloc(sizeof(*data));
> + data = g_malloc0(sizeof(*data));
> data->ret = ret;
> + error_setg(&data->blocker, "mirror job exiting");
> + bdrv_op_block(bs, BLOCK_OP_TYPE_DEVICE_IO, data->blocker);
> block_job_defer_to_main_loop(&s->common, mirror_exit, data);
> }
>
>
next prev parent reply other threads:[~2015-05-19 8:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 11:49 [Qemu-devel] [PATCH v4 00/13] Fix transactional snapshot with dataplane and NBD export Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 01/13] block: Add op blocker type "device IO" Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 02/13] block: Add op blocker notifier list Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 03/13] block-backend: Add blk_op_blocker_add_notifier Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 04/13] virtio-blk: Move complete_request to 'ops' structure Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 05/13] virtio-blk: Don't handle output when there is "device IO" op blocker Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 06/13] virtio-scsi-dataplane: Add "device IO" op blocker listener Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 07/13] nbd-server: Clear "can_read" when "device io" blocker is set Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 08/13] blockdev: Block device IO during internal snapshot transaction Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 09/13] blockdev: Block device IO during external " Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 10/13] blockdev: Block device IO during drive-backup transaction Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 11/13] blockdev: Block device IO during blockdev-backup transaction Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 12/13] block: Block "device IO" during bdrv_drain and bdrv_drain_all Fam Zheng
2015-05-19 11:49 ` [Qemu-devel] [PATCH v4 13/13] block/mirror: Block "device IO" during mirror exit Fam Zheng
2015-05-19 8:04 ` Paolo Bonzini [this message]
2015-05-19 16:48 ` Fam Zheng
2015-05-19 8:49 ` Paolo Bonzini
2015-05-19 18:37 ` Fam Zheng
2015-05-19 10:57 ` Paolo Bonzini
2015-05-20 2:23 ` 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=555AEEA3.4080407@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=famz@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.