qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, armbru@redhat.com,
	eblake@redhat.com, mreitz@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v3] qcow2: add overlap check for bitmap directory
Date: Thu, 5 Jul 2018 12:46:22 +0200	[thread overview]
Message-ID: <20180705104622.GF3309@localhost.localdomain> (raw)
In-Reply-To: <20180705092139.776069-1-vsementsov@virtuozzo.com>

Am 05.07.2018 um 11:21 hat Vladimir Sementsov-Ogievskiy geschrieben:
> If it appropriate for 3.0, let's push it. If not - then for 3.1
> with fixed "since". Should I cc stable?
> 
> v3: - update Qcow2OverlapCheckFlags in qapi/block-core.json [Max]
> 
> v2: - squash 02 (indentation fix) to 01
>     - drop comment from qcow2_check_metadata_overlap()
>     - set @ign to QCOW2_OL_BITMAP_DIRECTORY for in-place case in
>       bitmap_list_store. I don't think non-inplace case should be changed,
>       as it don't touch active bitmap directory.
> 
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
>  qapi/block-core.json   | 21 ++++++++++++---------
>  block/qcow2.h          | 45 ++++++++++++++++++++++++---------------------
>  block/qcow2-bitmap.c   |  7 ++++++-
>  block/qcow2-refcount.c | 10 ++++++++++
>  block/qcow2.c          | 22 ++++++++++++++--------
>  5 files changed, 66 insertions(+), 39 deletions(-)
> 
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 90e554ed0f..e7393e0313 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -2695,18 +2695,21 @@
>  # @template: Specifies a template mode which can be adjusted using the other
>  #            flags, defaults to 'cached'
>  #
> +# @bitmap-directory: since 3.0
> +#
>  # Since: 2.9
>  ##
>  { 'struct': 'Qcow2OverlapCheckFlags',
> -  'data': { '*template':       'Qcow2OverlapCheckMode',
> -            '*main-header':    'bool',
> -            '*active-l1':      'bool',
> -            '*active-l2':      'bool',
> -            '*refcount-table': 'bool',
> -            '*refcount-block': 'bool',
> -            '*snapshot-table': 'bool',
> -            '*inactive-l1':    'bool',
> -            '*inactive-l2':    'bool' } }
> +  'data': { '*template':        'Qcow2OverlapCheckMode',
> +            '*main-header':     'bool',
> +            '*active-l1':       'bool',
> +            '*active-l2':       'bool',
> +            '*refcount-table':  'bool',
> +            '*refcount-block':  'bool',
> +            '*snapshot-table':  'bool',
> +            '*inactive-l1':     'bool',
> +            '*inactive-l2':     'bool',
> +            '*bitmap-directory': 'bool' } }

Did you intend to add two spaces to each line? Because this still isn't
aligned to the same column.

Kevin

  reply	other threads:[~2018-07-05 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  9:21 [Qemu-devel] [PATCH v3] qcow2: add overlap check for bitmap directory Vladimir Sementsov-Ogievskiy
2018-07-05 10:46 ` Kevin Wolf [this message]
2018-07-05 14:48   ` Vladimir Sementsov-Ogievskiy

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=20180705104622.GF3309@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=den@openvz.org \
    --cc=eblake@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --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).