From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
vsementsov@virtuozzo.com, Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 3/7] block/dirty-bitmaps: add block_dirty_bitmap_check function
Date: Fri, 1 Mar 2019 14:57:19 -0500 [thread overview]
Message-ID: <4ee8a7b7-d110-8253-2caa-c8f6ec105bba@redhat.com> (raw)
In-Reply-To: <66ebf636-43e1-f16a-bd05-e9a8a766d4bd@redhat.com>
On 3/1/19 2:36 PM, Eric Blake wrote:
> On 3/1/19 1:15 PM, John Snow wrote:
>> Instead of checking against busy, inconsistent, or read only directly,
>> use a check function with permissions bits that let us streamline the
>> checks without reproducing them in many places.
>>
>> Included in this patch are permissions changes that simply add the
>> inconsistent check to existing permissions call spots, without
>> addressing existing bugs.
>>
>> In general, this means that busy+readonly checks become BDRV_BITMAP_DEFAULT,
>> which checks against all three conditions. busy-only checks become
>> BDRV_BITMAP_ALLOW_RO.
>>
>> Notably, remove allows inconsistent bitmaps, so it doesn't follow the pattern.
>>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> ---
>> include/block/dirty-bitmap.h | 13 ++++++++-
>> block/dirty-bitmap.c | 38 +++++++++++++++++++-------
>> blockdev.c | 49 +++++++---------------------------
>> migration/block-dirty-bitmap.c | 12 +++------
>> nbd/server.c | 3 +--
>> 5 files changed, 54 insertions(+), 61 deletions(-)
>>
>
> Diffstat proves its a win, even with the extra documentation for the new
> function. Nice.
>
It would have been even more obvious if I had added the individual
"inconsistent" checks before conversion, so that it's even close to
breaking even seems like a win.
>> +int bdrv_dirty_bitmap_check(const BdrvDirtyBitmap *bitmap, uint32_t flags,
>> + Error **errp)
>> +{
>> + if ((flags & BDRV_BITMAP_BUSY) && bdrv_dirty_bitmap_busy(bitmap)) {
>> + error_setg(errp, "Bitmap '%s' is currently in use by another"
>> + " operation and cannot be used", bitmap->name);
>
> Split before space,
>
>> + return -1;
>> + }
>> +
>> + if ((flags & BDRV_BITMAP_RO) && bdrv_dirty_bitmap_readonly(bitmap)) {
>> + error_setg(errp, "Bitmap '%s' is readonly and cannot be modified",
>> + bitmap->name);
>> + return -1;
>> + }
>> +
>> + if ((flags & BDRV_BITMAP_INCONSISTENT) &&
>> + bdrv_dirty_bitmap_inconsistent(bitmap)) {
>> + error_setg(errp, "Bitmap '%s' is inconsistent and cannot be used",
>> + bitmap->name);
>> + error_append_hint(errp, "Try block-dirty-bitmap-remove to delete "
>> + "this bitmap from disk");
>
> split after space. Looks inconsistent within a single function (pardon
> the pun :)
>
Ah... I've never known how to split strings. In fact, does anyone?
I'll address this either in staging or as a follow-up, as I assume
Vladimir will have some comments for me.
--js
> That's minor,
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
Thanks!
next prev parent reply other threads:[~2019-03-01 19:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 19:15 [Qemu-devel] [PATCH v3 0/7] bitmaps: add inconsistent bit John Snow
2019-03-01 19:15 ` [Qemu-devel] [PATCH v3 1/7] block/dirty-bitmaps: " John Snow
2019-03-01 19:32 ` Eric Blake
2019-03-01 19:44 ` John Snow
2019-03-06 12:25 ` Vladimir Sementsov-Ogievskiy
2019-03-06 13:06 ` Vladimir Sementsov-Ogievskiy
2019-03-06 13:08 ` Vladimir Sementsov-Ogievskiy
2019-03-06 15:15 ` John Snow
2019-03-01 19:15 ` [Qemu-devel] [PATCH v3 2/7] block/dirty-bitmap: add inconsistent status John Snow
2019-03-06 13:05 ` Vladimir Sementsov-Ogievskiy
2019-03-06 15:14 ` John Snow
2019-03-01 19:15 ` [Qemu-devel] [PATCH v3 3/7] block/dirty-bitmaps: add block_dirty_bitmap_check function John Snow
2019-03-01 19:36 ` Eric Blake
2019-03-01 19:57 ` John Snow [this message]
2019-03-01 20:03 ` Eric Blake
2019-03-01 20:06 ` Eric Blake
2019-03-06 13:44 ` Vladimir Sementsov-Ogievskiy
2019-03-06 15:17 ` John Snow
2019-03-01 19:15 ` [Qemu-devel] [PATCH v3 4/7] block/dirty-bitmaps: prohibit readonly bitmaps for backups John Snow
2019-03-01 19:38 ` Eric Blake
2019-03-06 13:47 ` Vladimir Sementsov-Ogievskiy
2019-03-01 19:15 ` [Qemu-devel] [PATCH v3 5/7] block/dirty-bitmaps: prohibit removing readonly bitmaps John Snow
2019-03-01 19:39 ` Eric Blake
2019-03-06 13:49 ` Vladimir Sementsov-Ogievskiy
2019-03-01 19:15 ` [Qemu-devel] [PATCH v3 6/7] block/dirty-bitmaps: disallow busy bitmaps as merge source John Snow
2019-03-01 19:44 ` Eric Blake
2019-03-01 19:48 ` John Snow
2019-03-01 19:57 ` Eric Blake
2019-03-01 20:04 ` John Snow
2019-03-06 13:57 ` Vladimir Sementsov-Ogievskiy
2019-03-06 15:24 ` John Snow
2019-03-06 15:29 ` Eric Blake
2019-03-06 13:57 ` Vladimir Sementsov-Ogievskiy
2019-03-01 19:15 ` [Qemu-devel] [PATCH v3 7/7] block/dirty-bitmaps: implement inconsistent bit John Snow
2019-03-01 19:53 ` Eric Blake
2019-03-06 14:26 ` Vladimir Sementsov-Ogievskiy
2019-03-06 21:46 ` John Snow
2019-03-07 16:37 ` Eric Blake
2019-03-08 18:46 ` John Snow
2019-03-05 23:59 ` [Qemu-devel] [PATCH v3 0/7] bitmaps: add " 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=4ee8a7b7-d110-8253-2caa-c8f6ec105bba@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--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).