From: Max Reitz <mreitz@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block: implement the bdrv_reopen_prepare helper for LUKS driver
Date: Wed, 31 Jan 2018 19:27:38 +0100 [thread overview]
Message-ID: <23d13ff3-adfb-05ee-e09a-6ba072f1ff76@redhat.com> (raw)
In-Reply-To: <20180118103143.11780-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
On 2018-01-18 11:31, Daniel P. Berrange wrote:
> If the bdrv_reopen_prepare helper isn't provided, the qemu-img commit
> command fails to re-open the base layer after committing changes into
> it. Provide a no-op implementation for the LUKS driver, since there
> is not any custom work that needs doing to re-open it.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> block/crypto.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/block/crypto.c b/block/crypto.c
> index 60ddf8623e..bb9a8f5376 100644
> --- a/block/crypto.c
> +++ b/block/crypto.c
> @@ -382,6 +382,12 @@ static void block_crypto_close(BlockDriverState *bs)
> qcrypto_block_free(crypto->block);
> }
>
> +static int block_crypto_reopen_prepare(BDRVReopenState *state,
> + BlockReopenQueue *queue, Error **errp)
> +{
> + /* nothing needs checking */
> + return 0;
> +}
Unfortunately I have to admit I'm not quite an expert on reopen
myself... But generally it is used to change options, so in theory one
could provide a new key-secret here. It's up to you whether you want to
support that or not (with this implementation the user will get an error
when they want to change the key-secret).
Apart from that, I think a no-op should be OK.
Max
>
> /*
> * 1 MB bounce buffer gives good performance / memory tradeoff
> @@ -620,6 +626,7 @@ BlockDriver bdrv_crypto_luks = {
> .bdrv_truncate = block_crypto_truncate,
> .create_opts = &block_crypto_create_opts_luks,
>
> + .bdrv_reopen_prepare = block_crypto_reopen_prepare,
> .bdrv_refresh_limits = block_crypto_refresh_limits,
> .bdrv_co_preadv = block_crypto_co_preadv,
> .bdrv_co_pwritev = block_crypto_co_pwritev,
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2018-01-31 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 10:31 [Qemu-devel] [PATCH] block: implement the bdrv_reopen_prepare helper for LUKS driver Daniel P. Berrange
2018-01-18 19:51 ` Eric Blake
2018-01-19 9:25 ` Daniel P. Berrange
2018-01-31 18:27 ` Max Reitz [this message]
2018-02-16 13:53 ` Daniel P. Berrangé
2018-03-06 10:35 ` Daniel P. Berrangé
2018-03-06 11:18 ` Kevin Wolf
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=23d13ff3-adfb-05ee-e09a-6ba072f1ff76@redhat.com \
--to=mreitz@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@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).