From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, dplotnikov@virtuozzo.com,
vsementsov@virtuozzo.com, den@virtuozzo.com
Subject: Re: [Qemu-devel] [PATCH v2 2/3] mirror: Keep mirror_top_bs drained after dropping permissions
Date: Wed, 7 Aug 2019 23:26:59 +0200 [thread overview]
Message-ID: <b5fc43d9-6a67-38e9-d24a-93d5646fdf6d@redhat.com> (raw)
In-Reply-To: <20190807144628.4988-3-kwolf@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2090 bytes --]
On 07.08.19 16:46, Kevin Wolf wrote:
> mirror_top_bs is currently implicitly drained through its connection to
> the source or the target node. However, the drain section for target_bs
> ends early after moving mirror_top_bs from src to target_bs, so that
> requests can already be restarted while mirror_top_bs is still present
> in the chain, but has dropped all permissions and therefore runs into an
> assertion failure like this:
>
> qemu-system-x86_64: block/io.c:1634: bdrv_co_write_req_prepare:
> Assertion `child->perm & BLK_PERM_WRITE' failed.
>
> Keep mirror_top_bs drained until all graph changes have completed.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/mirror.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/block/mirror.c b/block/mirror.c
> index 9f5c59ece1..642d6570cc 100644
> --- a/block/mirror.c
> +++ b/block/mirror.c
> @@ -656,7 +656,10 @@ static int mirror_exit_common(Job *job)
> s->target = NULL;
>
> /* We don't access the source any more. Dropping any WRITE/RESIZE is
> - * required before it could become a backing file of target_bs. */
> + * required before it could become a backing file of target_bs. Not having
> + * these permissions any more means that we can't allow any new requests on
> + * mirror_top_bs from now on, so keep it drained. */
You’re lucky Patchew broke or it would have complained about multi-line
comments needing /* and */ on separate lines. :-)
I’m perfectly happy with this style, though:
Reviewed-by: Max Reitz <mreitz@redhat.com>
> + bdrv_drained_begin(mirror_top_bs);
> bs_opaque->stop = true;
> bdrv_child_refresh_perms(mirror_top_bs, mirror_top_bs->backing,
> &error_abort);
> @@ -724,6 +727,7 @@ static int mirror_exit_common(Job *job)
> bs_opaque->job = NULL;
>
> bdrv_drained_end(src);
> + bdrv_drained_end(mirror_top_bs);
> s->in_drain = false;
> bdrv_unref(mirror_top_bs);
> bdrv_unref(src);
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-07 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 14:46 [Qemu-devel] [PATCH v2 0/3] block-backend: Queue requests while drained Kevin Wolf
2019-08-07 14:46 ` [Qemu-devel] [PATCH v2 1/3] block: Remove blk_pread_unthrottled() Kevin Wolf
2019-08-07 14:46 ` [Qemu-devel] [PATCH v2 2/3] mirror: Keep mirror_top_bs drained after dropping permissions Kevin Wolf
2019-08-07 21:26 ` Max Reitz [this message]
2019-08-07 14:46 ` [Qemu-devel] [PATCH v2 3/3] block-backend: Queue requests while drained Kevin Wolf
2019-08-07 21:38 ` Max Reitz
2019-08-07 15:10 ` [Qemu-devel] [PATCH v2 0/3] " no-reply
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=b5fc43d9-6a67-38e9-d24a-93d5646fdf6d@redhat.com \
--to=mreitz@redhat.com \
--cc=den@virtuozzo.com \
--cc=dplotnikov@virtuozzo.com \
--cc=kwolf@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).