From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Lqo66-0001Rw-UD
	for qemu-devel@nongnu.org; Mon, 06 Apr 2009 08:38:42 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Lqo62-0001Qs-E2
	for qemu-devel@nongnu.org; Mon, 06 Apr 2009 08:38:42 -0400
Received: from [199.232.76.173] (port=38978 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Lqo62-0001Qn-7Y
	for qemu-devel@nongnu.org; Mon, 06 Apr 2009 08:38:38 -0400
Received: from verein.lst.de ([213.95.11.210]:56756)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60)
	(envelope-from <hch@lst.de>) id 1Lqo61-00034A-Ns
	for qemu-devel@nongnu.org; Mon, 06 Apr 2009 08:38:38 -0400
Date: Mon, 6 Apr 2009 14:38:32 +0200
From: Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH 05/10] xen: add block device backend driver.
Message-ID: <20090406123832.GA8806@lst.de>
References: <1238621982-18333-1-git-send-email-kraxel@redhat.com>
	<1238621982-18333-6-git-send-email-kraxel@redhat.com>
	<20090402170209.GA10089@lst.de> <49D8B702.5040807@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49D8B702.5040807@codemonkey.ws>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>

On Sun, Apr 05, 2009 at 08:49:54AM -0500, Anthony Liguori wrote:
> Christoph Hellwig wrote:
> >
> >
> >We already have bdrv_aio_readv/writev which currently linearize the
> >buffer underneath.  Hopefully Anthony will have commited the patch to
> >implement the real one while I'm writing this, too :)
> >  
> 
> Unless I missed it somehow, I'm still expecting another post from you to 
> fix the use-after-free and Win32 issues I raised on the 3/29 posting.

I assumes you wanted to fix the use after free that we found inline, but
I'll resend the series now.  After your removal the patch doesn't touch
win32 code anymore and I used the mingw32 cross-compiler to verify that
it still builds (it doesn't link either with or without my patches,
though)