From: Tuguoyi <tu.guoyi@h3c.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: Chengchiwen <chengchiwen@h3c.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-stable@nongnu.org" <qemu-stable@nongnu.org>,
Wangyongqing <w_yongqing@h3c.com>,
Changlimin <changlimin@h3c.com>, Gaoliang <liang_gao@h3c.com>,
Wangyong <wang.yongD@h3c.com>
Subject: RE: [PATCH v4] qcow2-bitmap: Fix uint64_t left-shift overflow
Date: Fri, 1 Nov 2019 09:34:33 +0000 [thread overview]
Message-ID: <7650a7b706d24774b4ea3af23a2b371f@h3c.com> (raw)
In-Reply-To: <8b7d3d50-4a29-a8b3-5b6c-cde4af1b1d7a@virtuozzo.com>
On 01.11.2019 17:25 Vladimir Sementsov-Ogievskiy wrote:
> 01.11.2019 10:37, Tuguoyi wrote:
> > There are two issues in In check_constraints_on_bitmap(),
> > 1) The sanity check on the granularity will cause uint64_t integer
> > left-shift overflow when cluster_size is 2M and the granularity is
> > BIGGER than 32K.
> > 2) The way to calculate image size that the maximum bitmap supported
> > can map to is a bit incorrect.
> > This patch fix it by add a helper function to calculate the number of
> > bytes needed by a normal bitmap in image and compare it to the maximum
> > bitmap bytes supported by qemu.
> >
> > Fixes: 5f72826e7fc62167cf3a
> > Signed-off-by: Guoyi Tu <tu.guoyi@h3c.com>
>
> You forget my
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Sorry for that, it's my first time to submit patch to qemu, and should I send another patch or not ?
> (I don't see changes except add "Fixes: " to commit msg and put
> get_bitmap_bytes_needed definition header into one line.)
Yes, Only minor changes are made, including removing 'inline' keyword.
Thanks for your patience in reviewing
> > ---
> > block/qcow2-bitmap.c | 14 +++++++++++---
> > 1 file changed, 11 insertions(+), 3 deletions(-)
> >
> > diff --git a/block/qcow2-bitmap.c b/block/qcow2-bitmap.c index
> > 98294a7..ef9ef62 100644
> > --- a/block/qcow2-bitmap.c
> > +++ b/block/qcow2-bitmap.c
> > @@ -142,6 +142,13 @@ static int check_table_entry(uint64_t entry, int
> cluster_size)
> > return 0;
> > }
> >
> > +static int64_t get_bitmap_bytes_needed(int64_t len, uint32_t
> > +granularity) {
> > + int64_t num_bits = DIV_ROUND_UP(len, granularity);
> > +
> > + return DIV_ROUND_UP(num_bits, 8); }
> > +
> > static int check_constraints_on_bitmap(BlockDriverState *bs,
> > const char *name,
> > uint32_t granularity, @@
> > -150,6 +157,7 @@ static int check_constraints_on_bitmap(BlockDriverState
> *bs,
> > BDRVQcow2State *s = bs->opaque;
> > int granularity_bits = ctz32(granularity);
> > int64_t len = bdrv_getlength(bs);
> > + int64_t bitmap_bytes;
> >
> > assert(granularity > 0);
> > assert((granularity & (granularity - 1)) == 0); @@ -171,9 +179,9
> > @@ static int check_constraints_on_bitmap(BlockDriverState *bs,
> > return -EINVAL;
> > }
> >
> > - if ((len > (uint64_t)BME_MAX_PHYS_SIZE << granularity_bits) ||
> > - (len > (uint64_t)BME_MAX_TABLE_SIZE * s->cluster_size <<
> > - granularity_bits))
> > + bitmap_bytes = get_bitmap_bytes_needed(len, granularity);
> > + if ((bitmap_bytes > (uint64_t)BME_MAX_PHYS_SIZE) ||
> > + (bitmap_bytes > (uint64_t)BME_MAX_TABLE_SIZE *
> > + s->cluster_size))
> > {
> > error_setg(errp, "Too much space will be occupied by the
> bitmap. "
> > "Use larger granularity");
> >
>
>
> --
> Best regards,
> Vladimir
next prev parent reply other threads:[~2019-11-01 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 7:37 [PATCH v4] qcow2-bitmap: Fix uint64_t left-shift overflow Tuguoyi
2019-11-01 9:21 ` Vladimir Sementsov-Ogievskiy
2019-11-01 9:34 ` Tuguoyi [this message]
2019-11-01 10:09 ` Vladimir Sementsov-Ogievskiy
2019-11-02 2:27 ` Tuguoyi
2019-11-05 16:24 ` Max Reitz
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=7650a7b706d24774b4ea3af23a2b371f@h3c.com \
--to=tu.guoyi@h3c.com \
--cc=changlimin@h3c.com \
--cc=chengchiwen@h3c.com \
--cc=kwolf@redhat.com \
--cc=liang_gao@h3c.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=vsementsov@virtuozzo.com \
--cc=w_yongqing@h3c.com \
--cc=wang.yongD@h3c.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).