From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
Max Reitz <mreitz@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [PATCH v7 00/14] LUKS: encryption slot management using amend interface
Date: Fri, 29 May 2020 10:59:44 +0100 [thread overview]
Message-ID: <20200529095944.GC2755532@redhat.com> (raw)
In-Reply-To: <20200518122041.10694-1-mlevitsk@redhat.com>
On Mon, May 18, 2020 at 03:20:27PM +0300, Maxim Levitsky wrote:
> Hi!
> Here is the updated series of my patches, incorporating all the feedback I received.
>
> This implements the API interface that we agreed upon except that I merged the
> LUKSKeyslotActive/LUKSKeyslotInactive union into a struct because otherwise
> I need nested unions which are not supported currently by QAPI parser.
> This didn't change the API and thus once support for nested unions is there,
> it can always be implemented in backward compatible way.
>
> I hope that this series will finally be considered for merging, since I am somewhat running
> out of time to finish this task.
>
> Patches are strictly divided by topic to 3 groups, and each group depends on former groups.
>
> * Patches 1,2 implement qcrypto generic amend interface, including definition
> of structs used in crypto.json and implement this in luks crypto driver
> Nothing is exposed to the user at this stage
>
> * Patches 3-9 use the code from patches 1,2 to implement qemu-img amend based encryption slot management
> for luks and for qcow2, and add a bunch of iotests to cover that.
>
> * Patches 10-13 add x-blockdev-amend (I'll drop the -x prefix if you like), and wire it
> to luks and qcow2 driver to implement qmp based encryption slot management also using
> the code from patches 1,2, and also add a bunch of iotests to cover this.
>
> Tested with -raw,-qcow2,-nbd and -luks iotests and 'make check'
>
> Changes from V4:
> * Addresed feedback on patch 2 from Daniel (thanks!)
> * Gave real numbers to the tests
> * Updated the copyright in amend.c to RedHat
> * Rebased and adjusted the python iotests to latest changes in iotest infrastructure
>
> Changes from V5:
> * Updated all QMP docs to state that all added QMP features are since 5.1
> * Rebased to latest master
>
> Changes from V6:
> * Addressed most of the review feedback from Max Reitz
> * Rebased on latest qemu master
It needs another rebase as there's some conflicts now.
In any case, all the patches have my R-B already, and I don't have
any further comments to add.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-05-29 10:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 12:20 [PATCH v7 00/14] LUKS: encryption slot management using amend interface Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 01/14] qcrypto/core: add generic infrastructure for crypto options amendment Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 02/14] qcrypto/luks: implement encryption key management Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 03/14] block/amend: add 'force' option Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 04/14] block/amend: separate amend and create options for qemu-img Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 05/14] block/amend: refactor qcow2 amend options Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 06/14] block/crypto: rename two functions Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 07/14] block/crypto: implement the encryption key management Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 08/14] block/qcow2: extend qemu-img amend interface with crypto options Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 09/14] iotests: filter few more luks specific create options Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 10/14] iotests: qemu-img tests for luks key management Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 11/14] block/core: add generic infrastructure for x-blockdev-amend qmp command Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 12/14] block/crypto: implement blockdev-amend Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 13/14] block/qcow2: " Maxim Levitsky
2020-05-18 12:20 ` [PATCH v7 14/14] iotests: add tests for blockdev-amend Maxim Levitsky
2020-05-18 15:50 ` [PATCH v7 00/14] LUKS: encryption slot management using amend interface no-reply
2020-05-18 23:04 ` no-reply
2020-05-29 9:59 ` Daniel P. Berrangé [this message]
2020-06-02 16:29 ` Max Reitz
2020-06-07 13:06 ` Maxim Levitsky
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=20200529095944.GC2755532@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@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).