qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Qemu-block] [PATCH v6 00/11] Add new LUKS block driver


From: Kevin Wolf
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v6 00/11] Add new LUKS block driver (for 2.6)
Date: Tue, 29 Mar 2016 11:13:55 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

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.

Kevin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]