From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: dplotnikov@virtuozzo.com, vsementsov@virtuozzo.com,
den@virtuozzo.com, mreitz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] mirror: Keep target drained until graph changes are done
Date: Thu, 25 Jul 2019 12:03:57 -0500 [thread overview]
Message-ID: <cb7ded03-37df-2ef1-4fc5-113e15ff36c1@redhat.com> (raw)
In-Reply-To: <20190725162704.12622-4-kwolf@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1691 bytes --]
On 7/25/19 11:27 AM, Kevin Wolf wrote:
> Calling bdrv_drained_end() for target_bs can restarts requests too
restart
> early, so that they would execute on mirror_top_bs, which however has
> already dropped all permissions.
>
> Keep the target node drained until all graph changes have completed.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/mirror.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/block/mirror.c b/block/mirror.c
> index 8cb75fb409..7483051f8d 100644
> --- a/block/mirror.c
> +++ b/block/mirror.c
> @@ -644,6 +644,11 @@ static int mirror_exit_common(Job *job)
> bdrv_ref(mirror_top_bs);
> bdrv_ref(target_bs);
>
> + /* The mirror job has no requests in flight any more, but we need to
> + * drain potential other users of the BDS before changing the graph. */
Is checkpatch going to gripe about your comment style,
> + assert(s->in_drain);
> + bdrv_drained_begin(target_bs);
> +
> /* Remove target parent that still uses BLK_PERM_WRITE/RESIZE before
> * inserting target_bs at s->to_replace, where we might not be able to get
> * these permissions.
> @@ -684,12 +689,7 @@ static int mirror_exit_common(Job *job)
> bdrv_reopen_set_read_only(target_bs, ro, NULL);
> }
>
> - /* The mirror job has no requests in flight any more, but we need to
> - * drain potential other users of the BDS before changing the graph. */
even though it is just code motion?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-25 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 16:27 [Qemu-devel] [PATCH 0/4] block-backend: Queue requests while drained Kevin Wolf
2019-07-25 16:27 ` [Qemu-devel] [PATCH 1/4] block: Remove blk_pread_unthrottled() Kevin Wolf
2019-07-26 9:18 ` Max Reitz
2019-07-25 16:27 ` [Qemu-devel] [PATCH 2/4] block: Reduce (un)drains when replacing a child Kevin Wolf
2019-07-25 16:27 ` [Qemu-devel] [PATCH 3/4] mirror: Keep target drained until graph changes are done Kevin Wolf
2019-07-25 17:03 ` Eric Blake [this message]
2019-07-26 9:52 ` Max Reitz
2019-07-26 11:36 ` Kevin Wolf
2019-07-26 12:30 ` Max Reitz
2019-07-25 16:27 ` [Qemu-devel] [PATCH 4/4] block-backend: Queue requests while drained Kevin Wolf
2019-07-25 17:06 ` Eric Blake
2019-07-26 10:50 ` Max Reitz
2019-07-26 11:49 ` Kevin Wolf
2019-07-26 12:34 ` Max Reitz
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=cb7ded03-37df-2ef1-4fc5-113e15ff36c1@redhat.com \
--to=eblake@redhat.com \
--cc=den@virtuozzo.com \
--cc=dplotnikov@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).