From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 4/4] block: Use blk_make_empty() after commits
Date: Tue, 28 Apr 2020 09:07:44 -0500 [thread overview]
Message-ID: <0fb5d21f-4075-8c6a-0105-01fc60acaecf@redhat.com> (raw)
In-Reply-To: <20200428132629.796753-5-mreitz@redhat.com>
On 4/28/20 8:26 AM, Max Reitz wrote:
> bdrv_commit() already has a BlockBackend pointing to the BDS that we
> want to empty, it just has the wrong permissions.
>
> qemu-img commit has no BlockBackend pointing to the old backing file
> yet, but introducing one is simple.
>
> After this commit, bdrv_make_empty() is the only remaining caller of
> BlockDriver.bdrv_make_empty().
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> block/commit.c | 8 +++++++-
> qemu-img.c | 19 ++++++++++++++-----
> 2 files changed, 21 insertions(+), 6 deletions(-)
>
> diff --git a/block/commit.c b/block/commit.c
> index 8e672799af..24720ba67d 100644
> --- a/block/commit.c
> +++ b/block/commit.c
> @@ -493,10 +493,16 @@ int bdrv_commit(BlockDriverState *bs)
> }
>
> if (drv->bdrv_make_empty) {
This 'if' is still a bit awkward. Do all filter drivers set this
function, or will bdrv_make_empty() automatically take care of looking
through filters? Should this be a check of a supported_ variable
instead (similar to how Kevin just added supported_truncate_flags)?
> - ret = drv->bdrv_make_empty(bs);
> + ret = blk_set_perm(src, BLK_PERM_WRITE, BLK_PERM_ALL, NULL);
> if (ret < 0) {
> goto ro_cleanup;
> }
> +
> + ret = blk_make_empty(src, NULL);
So, if the driver lacks the callback, you miss calling blk_make_empty()
even if it would have done something.
> + if (ret < 0) {
> + goto ro_cleanup;
> + }
> +
> blk_flush(src);
> }
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 821cbf610e..a5e8659867 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -1065,11 +1065,20 @@ static int img_commit(int argc, char **argv)
> goto unref_backing;
> }
>
> - if (!drop && bs->drv->bdrv_make_empty) {
> - ret = bs->drv->bdrv_make_empty(bs);
Old code: if the driver had the callback, use it.
> - if (ret) {
> - error_setg_errno(&local_err, -ret, "Could not empty %s",
> - filename);
> + if (!drop) {
> + BlockBackend *old_backing_blk;
> +
> + old_backing_blk = blk_new_with_bs(bs, BLK_PERM_WRITE, BLK_PERM_ALL,
> + &local_err);
> + if (!old_backing_blk) {
> + goto unref_backing;
> + }
> + ret = blk_make_empty(old_backing_blk, &local_err);
New code: Call blk_make_empty() whether or not driver has the callback,
then deal with the fallout.
> + blk_unref(old_backing_blk);
> + if (ret == -ENOTSUP) {
> + error_free(local_err);
> + local_err = NULL;
> + } else if (ret < 0) {
> goto unref_backing;
> }
But this actually looks smarter than the commit case.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-04-28 14:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 13:26 [PATCH 0/4] block: Do not call BlockDriver.bdrv_make_empty() directly Max Reitz
2020-04-28 13:26 ` [PATCH 1/4] block: Add bdrv_make_empty() Max Reitz
2020-04-28 13:53 ` Eric Blake
2020-04-28 14:01 ` Kevin Wolf
2020-04-28 14:07 ` Eric Blake
2020-04-28 14:16 ` Kevin Wolf
2020-04-28 14:25 ` Eric Blake
2020-04-28 14:21 ` Kevin Wolf
2020-04-29 7:39 ` Max Reitz
2020-04-28 13:26 ` [PATCH 2/4] block: Use bdrv_make_empty() where possible Max Reitz
2020-04-28 13:54 ` Eric Blake
2020-04-28 15:03 ` Kevin Wolf
2020-04-28 13:26 ` [PATCH 3/4] block: Add blk_make_empty() Max Reitz
2020-04-28 13:55 ` Eric Blake
2020-04-28 14:28 ` Eric Blake
2020-04-28 14:47 ` Kevin Wolf
2020-04-29 7:39 ` Max Reitz
2020-04-28 13:26 ` [PATCH 4/4] block: Use blk_make_empty() after commits Max Reitz
2020-04-28 14:07 ` Eric Blake [this message]
2020-04-29 7:58 ` Max Reitz
2020-04-28 15:03 ` Kevin Wolf
2020-04-29 8:01 ` Max Reitz
2020-04-28 13:38 ` [PATCH 0/4] block: Do not call BlockDriver.bdrv_make_empty() directly no-reply
2020-04-28 13:43 ` no-reply
2020-04-28 13:57 ` Eric Blake
2020-04-28 13:48 ` no-reply
2020-04-28 13:49 ` Eric Blake
2020-04-28 14:05 ` Eric Blake
2020-04-28 14:53 ` no-reply
2020-04-28 14:57 ` no-reply
2020-04-28 15:02 ` 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=0fb5d21f-4075-8c6a-0105-01fc60acaecf@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).