From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47079)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1aijE5-00028f-Qd
	for qemu-devel@nongnu.org; Wed, 23 Mar 2016 09:53:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1aijE4-0000KG-Ou
	for qemu-devel@nongnu.org; Wed, 23 Mar 2016 09:53:33 -0400
Date: Wed, 23 Mar 2016 14:53:23 +0100
From: Kevin Wolf <kwolf@redhat.com>
Message-ID: <20160323135323.GE4126@noname.redhat.com>
References: <1458569512-22970-1-git-send-email-berrange@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1458569512-22970-1-git-send-email-berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 00/11] Add new LUKS block driver (for
	2.6)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org, qemu-block@nongnu.org

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.

Kevin