From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [PATCH v2 0/4] luks: add qemu-img measure support
Date: Thu, 9 Jan 2020 11:10:08 +0000 [thread overview]
Message-ID: <20200109111012.559052-1-stefanha@redhat.com> (raw)
v2:
* Fix uint64_t <-> size_t type mismatch in block_crypto_measure() so that
32-bit builds pass
This patch series adds qemu-img measure support to the "luks" block driver. We
just need to take into account the LUKS header when sizing the image.
Stefan Hajnoczi (4):
luks: extract block_crypto_calculate_payload_offset()
luks: implement .bdrv_measure()
qemu-img: allow qemu-img measure --object without a filename
iotests: add 282 luks qemu-img measure test
block/crypto.c | 146 +++++++++++++++++++++++++++++++++++++
block/crypto.h | 5 ++
block/qcow2.c | 59 +--------------
qemu-img.c | 6 +-
tests/qemu-iotests/282 | 93 +++++++++++++++++++++++
tests/qemu-iotests/282.out | 30 ++++++++
tests/qemu-iotests/group | 1 +
7 files changed, 281 insertions(+), 59 deletions(-)
create mode 100755 tests/qemu-iotests/282
create mode 100644 tests/qemu-iotests/282.out
--
2.24.1
next reply other threads:[~2020-01-09 11:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 11:10 Stefan Hajnoczi [this message]
2020-01-09 11:10 ` [PATCH v2 1/4] luks: extract block_crypto_calculate_payload_offset() Stefan Hajnoczi
2020-01-14 15:25 ` Max Reitz
2020-01-15 13:40 ` Stefan Hajnoczi
2020-01-15 14:35 ` Max Reitz
2020-01-09 11:10 ` [PATCH v2 2/4] luks: implement .bdrv_measure() Stefan Hajnoczi
2020-01-14 15:43 ` Max Reitz
2020-01-15 13:41 ` Stefan Hajnoczi
2020-01-09 11:10 ` [PATCH v2 3/4] qemu-img: allow qemu-img measure --object without a filename Stefan Hajnoczi
2020-01-14 15:44 ` Max Reitz
2020-01-09 11:10 ` [PATCH v2 4/4] iotests: add 282 luks qemu-img measure test Stefan Hajnoczi
2020-01-14 15:48 ` 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=20200109111012.559052-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).