From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42396) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1akpjy-0001Ns-6r for qemu-devel@nongnu.org; Tue, 29 Mar 2016 05:15:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1akpjx-0005FF-1r for qemu-devel@nongnu.org; Tue, 29 Mar 2016 05:15:10 -0400 Date: Tue, 29 Mar 2016 10:15:00 +0100 From: "Daniel P. Berrange" Message-ID: <20160329091500.GE29697@redhat.com> References: <1458569512-22970-1-git-send-email-berrange@redhat.com> <20160323135323.GE4126@noname.redhat.com> <20160329091355.GA4600@noname.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160329091355.GA4600@noname.redhat.com> Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v6 00/11] Add new LUKS block driver (for 2.6) Reply-To: "Daniel P. Berrange" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: Fam Zheng , qemu-devel@nongnu.org, qemu-block@nongnu.org On Tue, Mar 29, 2016 at 11:13:55AM +0200, Kevin Wolf wrote: > Am 23.03.2016 um 14:53 hat Kevin Wolf geschrieben: > > Am 21.03.2016 um 15:11 hat Daniel P. Berrange geschrieben: > > > This series is just the block layer parts needed to add > > > a LUKS driver to QEMU. It was previously posted as part > > > of the larger series > > > > > > v1: https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg04748.html > > > v2: https://lists.gnu.org/archive/html/qemu-block/2016-01/msg00534.html > > > v3: https://lists.gnu.org/archive/html/qemu-devel/2016-02/msg03176.html > > > v4: https://lists.gnu.org/archive/html/qemu-devel/2016-02/msg06552.html > > > v5: https://lists.gnu.org/archive/html/qemu-devel/2016-03/msg04397.html > > > > > > The crypto subsystem pieces that this series depends on have now > > > all been merged. > > > > > > In this posting I am only proposing merge of the generic LUKS > > > driver. This can be added as a layer above any of the existing > > > drivers for accessing LUKS formatted volumes. > > > > > > When creating new volumes, however, only the file backend can > > > be used, since the block driver API doesn't allow for arbitrary > > > stacking of protocols when creating images. > > > > > > The integration with the qcow2 driver to replace the existing > > > built-in AES-CBC code is dropped from this series, postponed > > > until the 2.7 development cycle. > > > > > > There is a QEMU I/O test 149 that exercises the LUKS driver > > > and checks for compatibility with the dm-crypt/cryptsetup > > > impl. > > > > Thanks, applied to the block branch. > > I need to drop patches 8 to 11 because they break qcow2 tests. Test case > updates are okay during hard freeze, so please send fixed versions of > these patches even after today. Yep, I saw that message about breakage and will work on a fix today and resubmit Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|