From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] qcow2: include LUKS payload overhead in qemu-img measure
Date: Tue, 15 Jan 2019 12:49:48 +0100 [thread overview]
Message-ID: <47717208-d514-b7dc-4ebb-844951938cce@redhat.com> (raw)
In-Reply-To: <20190115111007.27159-1-stefanha@redhat.com>
On 1/15/19 12:10 PM, Stefan Hajnoczi wrote:
> The LUKS payload has a significant size (>1 MB). It must be included in the
> qemu-img measure calculation so we arrive at the correct minimum image size.
>
> Stefan Hajnoczi (2):
> qcow2: include LUKS payload overhead in qemu-img measure
> iotests: add LUKS payload overhead to 178 qemu-img measure test
>
> block/qcow2.c | 51 +++++++++++++++++++++++++++++++-
> tests/qemu-iotests/178 | 8 +++++
> tests/qemu-iotests/178.out.qcow2 | 24 +++++++++++++++
> 3 files changed, 82 insertions(+), 1 deletion(-)
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2019-01-15 11:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 11:10 [Qemu-devel] [PATCH 0/2] qcow2: include LUKS payload overhead in qemu-img measure Stefan Hajnoczi
2019-01-15 11:10 ` [Qemu-devel] [PATCH 1/2] " Stefan Hajnoczi
2019-01-21 13:08 ` Max Reitz
2019-01-21 13:15 ` Max Reitz
2019-01-21 13:29 ` Max Reitz
2019-01-21 13:45 ` Daniel P. Berrangé
2019-01-21 14:46 ` Stefan Hajnoczi
2019-01-15 11:10 ` [Qemu-devel] [PATCH 2/2] iotests: add LUKS payload overhead to 178 qemu-img measure test Stefan Hajnoczi
2019-01-21 13:13 ` Max Reitz
2019-01-15 11:49 ` Philippe Mathieu-Daudé [this message]
2019-01-21 1:51 ` [Qemu-devel] [PATCH 0/2] qcow2: include LUKS payload overhead in qemu-img measure no-reply
2019-01-21 10:35 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=47717208-d514-b7dc-4ebb-844951938cce@redhat.com \
--to=philmd@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).