From: Eric Blake <eblake@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Max Reitz" <mreitz@redhat.com>, "John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH v5 01/14] qcrypto/core: add generic infrastructure for crypto options amendment
Date: Thu, 7 May 2020 11:09:43 -0500 [thread overview]
Message-ID: <08257b8a-ed70-1a6d-ffb9-20441b5af91f@redhat.com> (raw)
In-Reply-To: <20200507125414.2151-2-mlevitsk@redhat.com>
On 5/7/20 7:54 AM, Maxim Levitsky wrote:
> This will be used first to implement luks keyslot management.
>
> block_crypto_amend_opts_init will be used to convert
> qemu-img cmdline to QCryptoBlockAmendOptions
>
> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> +++ b/qapi/crypto.json
> @@ -309,3 +309,19 @@
> 'base': 'QCryptoBlockInfoBase',
> 'discriminator': 'format',
> 'data': { 'luks': 'QCryptoBlockInfoLUKS' } }
> +
> +
> +
> +##
> +# @QCryptoBlockAmendOptions:
> +#
> +# The options that are available for all encryption formats
> +# when amending encryption settings
> +#
> +# Since: 5.0
Looks like our mail crossed, my v4 review landed after you sent v5.
We'll still have to scrub this series for s/5.0/5.1/
> +##
> +{ 'union': 'QCryptoBlockAmendOptions',
> + 'base': 'QCryptoBlockOptionsBase',
> + 'discriminator': 'format',
> + 'data': {
> + } }
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-05-07 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 12:54 [PATCH v5 00/14] LUKS: encryption slot management using amend interface Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 01/14] qcrypto/core: add generic infrastructure for crypto options amendment Maxim Levitsky
2020-05-07 16:09 ` Eric Blake [this message]
2020-05-07 19:08 ` Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 02/14] qcrypto/luks: implement encryption key management Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 03/14] block/amend: add 'force' option Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 04/14] block/amend: separate amend and create options for qemu-img Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 05/14] block/amend: refactor qcow2 amend options Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 06/14] block/crypto: rename two functions Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 07/14] block/crypto: implement the encryption key management Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 08/14] block/qcow2: extend qemu-img amend interface with crypto options Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 09/14] iotests: filter few more luks specific create options Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 10/14] iotests: qemu-img tests for luks key management Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 11/14] block/core: add generic infrastructure for x-blockdev-amend qmp command Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 12/14] block/crypto: implement blockdev-amend Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 13/14] block/qcow2: " Maxim Levitsky
2020-05-07 12:54 ` [PATCH v5 14/14] iotests: add tests for blockdev-amend Maxim Levitsky
2020-05-07 15:29 ` [PATCH v5 00/14] LUKS: encryption slot management using amend interface no-reply
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=08257b8a-ed70-1a6d-ffb9-20441b5af91f@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mlevitsk@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).