From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: kwolf@redhat.com, fam@euphon.net, qemu-devel@nongnu.org,
mreitz@redhat.com, stefanha@redhat.com, den@openvz.org
Subject: Re: [PATCH v3 1/5] block/io: fix bdrv_co_block_status_above
Date: Wed, 20 May 2020 09:38:30 -0500 [thread overview]
Message-ID: <1dfda9f1-48cf-236c-65eb-7afc5daaa77c@redhat.com> (raw)
In-Reply-To: <20200520083520.25793-2-vsementsov@virtuozzo.com>
On 5/20/20 3:35 AM, Vladimir Sementsov-Ogievskiy wrote:
> bdrv_co_block_status_above has several design problems with handling
> short backing files:
>
> 1. With want_zeros=true, it may return ret with BDRV_BLOCK_ZERO but
> without BDRV_BLOCK_ALLOCATED flag, when actually short backing file
> which produces these after-EOF zeros is inside requested backing
> sequence.
>
> 2. With want_zero=false, it may return pnum=0 prior to actual EOF,
> because of EOF of short backing file.
>
> Fix these things, making logic about short backing files clearer.
>
> With fixed bdrv_block_status_above we also have to improve is_zero in
> qcow2 code, otherwise iotest 154 will fail, because with this patch we
> stop to merge zeros of different types (produced by fully unallocated
> in the whole backing chain regions vs produced by short backing files).
>
> Note also, that this patch leaves for another day the general problem
> around block-status: misuse of BDRV_BLOCK_ALLOCATED as is-fs-allocated
> vs go-to-backing.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> block/io.c | 39 ++++++++++++++++++++++++++++++---------
> block/qcow2.c | 16 ++++++++++++++--
> 2 files changed, 44 insertions(+), 11 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
> +++ b/block/qcow2.c
> @@ -3827,8 +3827,20 @@ static bool is_zero(BlockDriverState *bs, int64_t offset, int64_t bytes)
> if (!bytes) {
> return true;
> }
> - res = bdrv_block_status_above(bs, NULL, offset, bytes, &nr, NULL, NULL);
> - return res >= 0 && (res & BDRV_BLOCK_ZERO) && nr == bytes;
> +
> + /*
> + * bdrv_block_status_above doesn't merge different types of zeros, for
> + * example, zeros which comes from the region which is unallocated in
s/comes/come/
> + * the whole backing chain, and zeros which comes because of short backing
and again, also s/of/of a/
> + * file. So, we need a loop.
> + */
> + do {
> + res = bdrv_block_status_above(bs, NULL, offset, bytes, &nr, NULL, NULL);
> + offset += nr;
> + bytes -= nr;
> + } while (res >= 0 && (res & BDRV_BLOCK_ZERO) && nr && bytes);
> +
> + return res >= 0 && (res & BDRV_BLOCK_ZERO) && bytes == 0;
> }
>
> static coroutine_fn int qcow2_co_pwrite_zeroes(BlockDriverState *bs,
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-05-20 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 8:35 [PATCH v3 0/5] fix & merge block_status_above and is_allocated_above Vladimir Sementsov-Ogievskiy
2020-05-20 8:35 ` [PATCH v3 1/5] block/io: fix bdrv_co_block_status_above Vladimir Sementsov-Ogievskiy
2020-05-20 14:38 ` Eric Blake [this message]
2020-05-20 8:35 ` [PATCH v3 2/5] block/io: bdrv_common_block_status_above: support include_base Vladimir Sementsov-Ogievskiy
2020-05-20 16:26 ` Eric Blake
2020-05-20 8:35 ` [PATCH v3 3/5] block/io: bdrv_common_block_status_above: support bs == base Vladimir Sementsov-Ogievskiy
2020-05-20 16:30 ` Eric Blake
2020-05-20 8:35 ` [PATCH v3 4/5] block/io: fix bdrv_is_allocated_above Vladimir Sementsov-Ogievskiy
2020-05-20 16:36 ` Eric Blake
2020-05-20 8:35 ` [PATCH v3 5/5] iotests: add commit top->base cases to 274 Vladimir Sementsov-Ogievskiy
2020-05-20 16:39 ` Eric Blake
2020-05-21 11:08 ` Vladimir Sementsov-Ogievskiy
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=1dfda9f1-48cf-236c-65eb-7afc5daaa77c@redhat.com \
--to=eblake@redhat.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).