From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.8 v2] hbitmap: Fix shifts of constants by granularity
Date: Tue, 29 Nov 2016 17:49:52 +0800 [thread overview]
Message-ID: <20161129094952.GD15786@lemon> (raw)
In-Reply-To: <20161115224732.1334-1-mreitz@redhat.com>
On Tue, 11/15 23:47, Max Reitz wrote:
> An hbitmap's granularity may be anything from 0 to 63, so when shifting
> constants by its value, they should not be plain ints.
>
> Even having changed the types, hbitmap_serialization_granularity() still
> tries to shift 64 to the right by the granularity. This operation is
> undefined if the granularity is greater than 57. Adding an assertion is
> fine for now, because serializing is done only in tests so far, but this
> means that only bitmaps with a granularity below 58 can be serialized
> and we should thus add a hbitmap_is_serializable() function later.
>
> One of the two places touched in this patch uses
> QEMU_ALIGN_UP(x, 1 << y). We can use ROUND_UP() there, since the second
> parameter is obviously a power of two.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> v2:
> - Fix the same issue in hbitmap_truncate() [Stefan]
> - Use ROUND_UP() instead of QEMU_ALIGN_UP() there (because we can)
> - Add an assertion to hbitmap_serialization_granularity() guaranteeing
> that the shift doesn't overflow; we can guarantee this so far because
> the only place where serialization functions are used in is the
> hbitmap test
> (I'll send a follow-up patch to allow users to check whether a certain
> bitmap can be (de-)serialized)
Thanks, queued.
I'll send a pull request soon.
Fam
> ---
> util/hbitmap.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/util/hbitmap.c b/util/hbitmap.c
> index 5d1a21c..9f691b7 100644
> --- a/util/hbitmap.c
> +++ b/util/hbitmap.c
> @@ -399,9 +399,13 @@ bool hbitmap_get(const HBitmap *hb, uint64_t item)
>
> uint64_t hbitmap_serialization_granularity(const HBitmap *hb)
> {
> + /* Must hold true so that the shift below is defined
> + * (ld(64) == 6, i.e. 1 << 6 == 64) */
> + assert(hb->granularity < 64 - 6);
> +
> /* Require at least 64 bit granularity to be safe on both 64 bit and 32 bit
> * hosts. */
> - return 64 << hb->granularity;
> + return UINT64_C(64) << hb->granularity;
> }
>
> /* Start should be aligned to serialization granularity, chunk size should be
> @@ -594,7 +598,7 @@ void hbitmap_truncate(HBitmap *hb, uint64_t size)
> if (shrink) {
> /* Don't clear partial granularity groups;
> * start at the first full one. */
> - uint64_t start = QEMU_ALIGN_UP(num_elements, 1 << hb->granularity);
> + uint64_t start = ROUND_UP(num_elements, UINT64_C(1) << hb->granularity);
> uint64_t fix_count = (hb->size << hb->granularity) - start;
>
> assert(fix_count);
> --
> 2.10.2
>
prev parent reply other threads:[~2016-11-29 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 22:47 [Qemu-devel] [PATCH for-2.8 v2] hbitmap: Fix shifts of constants by granularity Max Reitz
2016-11-17 10:35 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-11-29 9:49 ` Fam Zheng [this message]
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=20161129094952.GD15786@lemon \
--to=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).