From: John Snow <jsnow@redhat.com>
To: 13466399134@163.com, qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] block/dirty-bitmap: Useless bitmaps in image can be removed
Date: Mon, 25 Jun 2018 13:40:39 -0400 [thread overview]
Message-ID: <ec4fc783-78b4-ba71-e36e-73149a2f7b06@redhat.com> (raw)
In-Reply-To: <20180625033643.14404-1-13466399134@163.com>
On 06/24/2018 11:36 PM, 13466399134@163.com wrote:
> If qemu-kvm quit without saving bitmaps to image(coredump, host kernel panic,
> or host pooweroff), bitmaps in image can not be safely used anymore, and also
> can not be removed. Useless bitmaps should be removed.
>
> Signed-off-by: yaoxu <13466399134@163.com>
I count at least ten copies of this same patch in my inbox. Please send
just ONE copy, and make sure it has [PATCH] in the title, like other
patches do.
> ---
> diff --git a/blockdev.c b/blockdev.c
> index 58d7570932..c85056a74b 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -2837,31 +2837,35 @@ void qmp_block_dirty_bitmap_remove(const char *node, const char *name,
> Error *local_err = NULL;
>
> bitmap = block_dirty_bitmap_lookup(node, name, &bs, errp);
> - if (!bitmap || !bs) {
> + if (!bs) {
In what cases are we going to fail to find a bitmap but manage to return
a BlockDriverState?
> return;
> }
>
> - if (bdrv_dirty_bitmap_frozen(bitmap)) {
> - error_setg(errp,
> - "Bitmap '%s' is currently frozen and cannot be removed",
> - name);
> - return;
> - } else if (bdrv_dirty_bitmap_qmp_locked(bitmap)) {
> - error_setg(errp,
> - "Bitmap '%s' is currently locked and cannot be removed",
> - name);
> + if (bitmap) {
> + if (bdrv_dirty_bitmap_frozen(bitmap)) {
> + error_setg(errp,
> + "Bitmap '%s' is currently frozen and cannot be removed",
> + name);
> + return;
> + } else if (bdrv_dirty_bitmap_qmp_locked(bitmap)) {
> + error_setg(errp,
> + "Bitmap '%s' is currently locked and cannot be removed",
> + name);
> + return;
> + }
> + }
> +
> + bdrv_remove_persistent_dirty_bitmap(bs, name, &local_err);
> + if (local_err != NULL) {
> + error_propagate(errp, local_err);
> return;
> }
>
> - if (bdrv_dirty_bitmap_get_persistance(bitmap)) {
> - bdrv_remove_persistent_dirty_bitmap(bs, name, &local_err);
> - if (local_err != NULL) {
> - error_propagate(errp, local_err);
> - return;
> - }
> + if (bitmap) {
> + bdrv_release_dirty_bitmap(bs, bitmap);
> }
>
> - bdrv_release_dirty_bitmap(bs, bitmap);
> + if (*errp) {
> + error_free(*errp);
> + *errp = NULL;
> + }
> }
>
> /**
>
Even if bitmap was null and bs was set, this is going to forward
requests for any bitmap, whether it exists or not, straight along to the
persistence layer, which does not give you an error if the bitmap didn't
exist.
We also can't open images with corrupted bitmaps in them for editing, so
this won't work there, either.
We are otherwise aware of the problem and intend to address it via
`qemu-img check -r`.
--js
next prev parent reply other threads:[~2018-06-25 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 3:36 [Qemu-devel] block/dirty-bitmap: Useless bitmaps in image can be removed 13466399134
2018-06-25 17:40 ` John Snow [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-25 2:47 yaoxu
2018-06-25 2:46 yaoxu
2018-06-25 2:36 13466399134
2018-06-25 2:35 13466399134
2018-06-25 2:31 yaoxu
2018-06-24 16:04 yaoxu
2018-06-24 16:01 yaoxu
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=ec4fc783-78b4-ba71-e36e-73149a2f7b06@redhat.com \
--to=jsnow@redhat.com \
--cc=13466399134@163.com \
--cc=armbru@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).