From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>, famz@redhat.com
Cc: Kevin Wolf <kwolf@redhat.com>, Benoit Canet <benoit@irqsave.net>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jd <jd_jedi@convirture.com>, Paolo Bonzini <pbonzini@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 05/10] block: Add bdrv_copy_dirty_bitmap and bdrv_reset_dirty_bitmap
Date: Mon, 17 Nov 2014 14:18:44 -0500 [thread overview]
Message-ID: <546A4A14.3040001@redhat.com> (raw)
In-Reply-To: <545CE25B.9030208@parallels.com>
On 11/07/2014 10:16 AM, Vladimir Sementsov-Ogievskiy wrote:
> from [PATCH v6 02/10]
>> +void qmp_block_dirty_bitmap_remove(const char *device, const char *name,
>> + Error **errp)
>> +{
>> + BlockDriverState *bs;
>> + BdrvDirtyBitmap *bitmap;
>> +
>> + bs = bdrv_find(device);
>> + if (!bs) {
>> + error_set(errp, QERR_DEVICE_NOT_FOUND, device);
>> + return;
>> + }
>> +
>> + if (!name || name[0] == '\0') {
>> + error_setg(errp, "Bitmap name cannot be empty");
>> + return;
>> + }
>> + bitmap = bdrv_find_dirty_bitmap(bs, name);
>> + if (!bitmap) {
>> + error_setg(errp, "Dirty bitmap not found: %s", name);
>> + return;
>> + }
>> +
>> + bdrv_dirty_bitmap_make_anon(bs, bitmap);
>> + bdrv_release_dirty_bitmap(bs, bitmap);
>> +}
>
> from [PATCH v6 05/10]:
>> +void qmp_block_dirty_bitmap_enable(const char *device, const char *name,
>> + Error **errp)
>> +{
>> + BlockDriverState *bs;
>> + BdrvDirtyBitmap *bitmap;
>> +
>> + bs = bdrv_find(device);
>> + if (!bs) {
>> + error_set(errp, QERR_DEVICE_NOT_FOUND, device);
>> + return;
>> + }
>> +
>> + bitmap = bdrv_find_dirty_bitmap(bs, name);
>> + if (!bitmap) {
>> + error_setg(errp, "Dirty bitmap not found: %s", name);
>> + return;
>> + }
>> +
>> + bdrv_enable_dirty_bitmap(bs, bitmap);
>> +}
>> +
>> +void qmp_block_dirty_bitmap_disable(const char *device, const char *name,
>> + Error **errp)
>> +{
>> + BlockDriverState *bs;
>> + BdrvDirtyBitmap *bitmap;
>> +
>> + bs = bdrv_find(device);
>> + if (!bs) {
>> + error_set(errp, QERR_DEVICE_NOT_FOUND, device);
>> + return;
>> + }
>> +
>> + bitmap = bdrv_find_dirty_bitmap(bs, name);
>> + if (!bitmap) {
>> + error_setg(errp, "Dirty bitmap not found: %s", name);
>> + return;
>> + }
>> +
>> + bdrv_disable_dirty_bitmap(bs, bitmap);
>> +}
>> +
>
> there is one inconsistence:
>
> you have check
>> + if (!name || name[0] == '\0') {
>> + error_setg(errp, "Bitmap name cannot be empty");
>> + return;
>> + }
> when accessing bitmap in qmp_block_dirty_bitmap_remove, but not in
> qmp_block_dirty_bitmap_{enable,disable}.
In qmp_block_dirty_bitmap_{enable,disable} I don't think it's a problem
if we don't check the name here -- it just means that we're not going to
be able to find the name (since it's invalid) and the function will
error out anyway.
I don't think a change is warranted, necessarily, unless we factor out
the error checking: see below.
> Also, I think it'll be better to put similar part of these three
> functions into one separate function to avoid duplicates, like
>
> static BdrvDirtyBitmap *bitmap find_dirty_bitmap(const char *device, const char *name,
> Error **errp)
> {
> BlockDriverState *bs;
> BdrvDirtyBitmap *bitmap;
>
> // most simple error condition earlier
> if (!name || name[0] == '\0') {
> error_setg(errp, "Bitmap name cannot be empty");
> return NULL;
> }
>
> bs = bdrv_find(device);
> if (!bs) {
> error_set(errp, QERR_DEVICE_NOT_FOUND, device);
> return NULL;
> }
>
> bitmap = bdrv_find_dirty_bitmap(bs, name);
> if (!bitmap) {
> error_setg(errp, "Dirty bitmap not found: %s", name);
> return NULL;
> }
>
> return bitmap;
> }
>
I think normally I would agree, but since qmp_block_dirty_bitmap_remove
needs to use the BlockDriverState anyway, part of this error-checking
routine gets duplicated regardless, unless you add another return
parameter to give you the BlockDriverState back as well, and you lose
the single purpose nature of factoring it out.
I will keep the redundancy of the error-checking of this patch in mind
as I clean it up for v7...
> --
> Best regards,
> Vladimir
>
next prev parent reply other threads:[~2014-11-17 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 15:16 [Qemu-devel] [PATCH v6 05/10] block: Add bdrv_copy_dirty_bitmap and bdrv_reset_dirty_bitmap Vladimir Sementsov-Ogievskiy
2014-11-17 19:18 ` John Snow [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-30 3:22 [Qemu-devel] [PATCH v6 00/10] block: Incremental backup series Fam Zheng
2014-10-30 3:22 ` [Qemu-devel] [PATCH v6 05/10] block: Add bdrv_copy_dirty_bitmap and bdrv_reset_dirty_bitmap Fam Zheng
2014-11-04 10:08 ` 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=546A4A14.3040001@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit@irqsave.net \
--cc=famz@redhat.com \
--cc=jd_jedi@convirture.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.