From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Benoit Canet <benoit@irqsave.net>
Subject: Re: [Qemu-devel] [PATCH v4 1/9] qapi: Add optional field "name" to block dirty bitmap
Date: Thu, 27 Mar 2014 16:30:13 +0100 [thread overview]
Message-ID: <20140327153013.GA2441@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1395911388-31027-2-git-send-email-famz@redhat.com>
On Thu, Mar 27, 2014 at 05:09:40PM +0800, Fam Zheng wrote:
> @@ -5079,18 +5080,45 @@ bool bdrv_qiov_is_aligned(BlockDriverState *bs, QEMUIOVector *qiov)
> return true;
> }
>
> -BdrvDirtyBitmap *bdrv_create_dirty_bitmap(BlockDriverState *bs, int granularity)
> +BdrvDirtyBitmap *bdrv_find_dirty_bitmap(BlockDriverState *bs, const char *name)
> +{
> + BdrvDirtyBitmap *bm;
> + QLIST_FOREACH(bm, &bs->dirty_bitmaps, list) {
> + if (!strcmp(name, bm->name)) {
> + return bm;
> + }
> + }
> + return NULL;
> +}
> +
> +void bdrv_dirty_bitmap_make_anon(BlockDriverState *bs, BdrvDirtyBitmap *bitmap)
> +{
> + g_free(bitmap->name);
> + bitmap->name = NULL;
> +}
This looks dangerous since strcmp() does not check for NULL pointers. I
guess you need to add a check to bdrv_find_dirty_bitmap().
> @@ -5120,6 +5149,8 @@ BlockDirtyInfoList *bdrv_query_dirty_bitmaps(BlockDriverState *bs)
> info->count = bdrv_get_dirty_count(bs, bm);
> info->granularity =
> ((int64_t) BDRV_SECTOR_SIZE << hbitmap_granularity(bm->bitmap));
> + info->has_name = bm->name[0] != '\0';
> + info->name = g_strdup(bm->name);
This looks dangerous too. What if ->name is NULL?
next prev parent reply other threads:[~2014-03-27 15:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 9:09 [Qemu-devel] [PATCH v4 0/9] QMP: Introduce incremental drive-backup with in-memory dirty bitmap Fam Zheng
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 1/9] qapi: Add optional field "name" to block " Fam Zheng
2014-03-27 15:30 ` Stefan Hajnoczi [this message]
2014-04-01 7:41 ` Fam Zheng
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 2/9] qmp: Add dirty-bitmap-add and dirty-bitmap-remove Fam Zheng
2014-03-27 15:43 ` Stefan Hajnoczi
2014-04-01 7:45 ` Fam Zheng
2014-03-27 16:09 ` Stefan Hajnoczi
2014-03-27 16:39 ` Dr. David Alan Gilbert
2014-04-01 7:48 ` Fam Zheng
2014-03-27 16:41 ` Eric Blake
2014-04-01 8:02 ` Fam Zheng
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 3/9] block: Handle error of bdrv_getlength in bdrv_create_dirty_bitmap Fam Zheng
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 4/9] block: Introduce bdrv_dirty_bitmap_granularity() Fam Zheng
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 5/9] hbitmap: Add hbitmap_copy Fam Zheng
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 6/9] block: Add bdrv_copy_dirty_bitmap and bdrv_reset_dirty_bitmap Fam Zheng
2014-03-28 8:04 ` Stefan Hajnoczi
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 7/9] qmp: Add dirty-bitmap-enable and dirty-bitmap-disable Fam Zheng
2014-03-27 16:46 ` Eric Blake
2014-04-01 8:16 ` Fam Zheng
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 8/9] qmp: Add support of "dirty-bitmap" sync mode for drive-backup Fam Zheng
2014-03-27 9:09 ` [Qemu-devel] [PATCH v4 9/9] qapi: Add transaction support to dirty-bitmap-{add, disable} Fam Zheng
2014-03-27 16:49 ` Eric Blake
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=20140327153013.GA2441@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=benoit@irqsave.net \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--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).