From: John Snow <jsnow@redhat.com>
To: qemu-stable@nongnu.org
Cc: qemu-block@nongnu.org, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, eblake@redhat.com,
vsementsov@virtuozzo.com, John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH v2] bitmap: Update count after a merge
Date: Tue, 2 Oct 2018 19:33:14 -0400 [thread overview]
Message-ID: <20181002233314.30159-1-jsnow@redhat.com> (raw)
From: Eric Blake <eblake@redhat.com>
We need an accurate count of the number of bits set in a bitmap
after a merge. In particular, since the merge operation short-circuits
a merge from an empty source, if you have bitmaps A, B, and C where
B started empty, then merge C into B, and B into A, an inaccurate
count meant that A did not get the contents of C.
In the worst case, we may falsely regard the bitmap as empty when
it has had new writes merged into it.
Fixes: be58721db
CC: qemu-stable@nongnu.org
Signed-off-by: Eric Blake <eblake@redhat.com>
Signed-off-by: John Snow <jsnow@redhat.com>
---
v2: based off of Eric's cover letter, now rebased properly
on top of the jsnow/bitmaps staging branch to use the
correct bitmap target (result).
util/hbitmap.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/util/hbitmap.c b/util/hbitmap.c
index d5aca5159f..8d402c59d9 100644
--- a/util/hbitmap.c
+++ b/util/hbitmap.c
@@ -759,6 +759,9 @@ bool hbitmap_merge(const HBitmap *a, const HBitmap *b, HBitmap *result)
}
}
+ /* Recompute the dirty count */
+ result->count = hb_count_between(result, 0, result->size - 1);
+
return true;
}
--
2.14.4
next reply other threads:[~2018-10-02 23:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 23:33 John Snow [this message]
2018-10-03 14:32 ` [Qemu-devel] [PATCH v2] bitmap: Update count after a merge Vladimir Sementsov-Ogievskiy
2018-10-03 14:49 ` Eric Blake
2018-10-03 19:57 ` John Snow
2018-10-03 20:01 ` Eric Blake
2018-10-04 12:06 ` Vladimir Sementsov-Ogievskiy
2018-10-03 20:48 ` John Snow
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=20181002233314.30159-1-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).