From: Kevin Wolf <kwolf@redhat.com>
To: oro@il.ibm.com
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, oro@il.ibm.com,
idryomov@gmail.com
Subject: Re: [PATCH v6 2/3] block/rbd: Add luks-any encryption opening option
Date: Thu, 23 Feb 2023 18:44:53 +0100 [thread overview]
Message-ID: <Y/el9QZDUtDNQfT3@redhat.com> (raw)
In-Reply-To: <20230129113120.722708-3-oro@oro.sl.cloud9.ibm.com>
Am 29.01.2023 um 12:31 hat ORO@il.ibm.com geschrieben:
> From: Or Ozeri <oro@il.ibm.com>
>
> Ceph RBD encryption API required specifying the encryption format
> for loading encryption. The supported formats were LUKS (v1) and LUKS2.
>
> Starting from Reef release, RBD also supports loading with "luks-any" format,
> which works for both versions of LUKS.
>
> This commit extends the qemu rbd driver API to enable qemu users to use
> this luks-any wildcard format.
>
> Signed-off-by: Or Ozeri <oro@il.ibm.com>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 95ac4fa634..e59fb5d453 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -3827,10 +3827,16 @@
> ##
> # @RbdImageEncryptionFormat:
> #
> +# luks
> +#
> +# luks2
If we don't want to document these values, there's no reason to have
them listed at all. After all, the undocumented list is already in the
definition.
> +# luks-any: Used for opening either luks or luks2. (Since 8.0)
And here it should be '@luks-any' with @.
> # Since: 6.1
> ##
> { 'enum': 'RbdImageEncryptionFormat',
> - 'data': [ 'luks', 'luks2' ] }
> + 'data': [ 'luks', 'luks2', 'luks-any' ] }
I've fixed this up and applied the series to my block branch. Thanks!
Kevin
next prev parent reply other threads:[~2023-02-23 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 11:31 [PATCH v6 0/3] block/rbd: Add support for layered encryption ORO@il.ibm.com
2023-01-29 11:31 ` [PATCH v6 1/3] block/rbd: Remove redundant stack variable passphrase_len ORO@il.ibm.com
2023-01-29 11:31 ` [PATCH v6 2/3] block/rbd: Add luks-any encryption opening option ORO@il.ibm.com
2023-02-23 17:44 ` Kevin Wolf [this message]
2023-01-29 11:31 ` [PATCH v6 3/3] block/rbd: Add support for layered encryption ORO@il.ibm.com
2023-01-30 13:16 ` [PATCH v6 0/3] " Ilya Dryomov
2023-02-22 20:13 ` Ilya Dryomov
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=Y/el9QZDUtDNQfT3@redhat.com \
--to=kwolf@redhat.com \
--cc=idryomov@gmail.com \
--cc=oro@il.ibm.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).