From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Lo2SL-00021O-Ma
	for qemu-devel@nongnu.org; Sun, 29 Mar 2009 17:22:13 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Lo2SH-0001y6-5k
	for qemu-devel@nongnu.org; Sun, 29 Mar 2009 17:22:13 -0400
Received: from [199.232.76.173] (port=52516 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Lo2SG-0001y1-PX
	for qemu-devel@nongnu.org; Sun, 29 Mar 2009 17:22:08 -0400
Received: from verein.lst.de ([213.95.11.210]:57765)
	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 1Lo2SG-0005HO-8t
	for qemu-devel@nongnu.org; Sun, 29 Mar 2009 17:22:08 -0400
Date: Sun, 29 Mar 2009 23:21:52 +0200
From: Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH 3/5] push down vector linearization
	to	posix-aio-compat.c
Message-ID: <20090329212152.GA4498@lst.de>
References: <20090329195346.GA625@lst.de> <20090329195452.GC1215@lst.de>
	<49CFE1A6.90509@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49CFE1A6.90509@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: Christoph Hellwig <hch@infradead.org>

On Sun, Mar 29, 2009 at 04:01:26PM -0500, Anthony Liguori wrote:
> This bug is not limited to win32 though.  It has to do with having a 
> backend disk format that does not provide a proper aio implement (which 
> suggests your new brv_aio_{readv,writev}_em at fault).  You can 
> reproduce on a normal Linux build by converting an existing image to a 
> format like vmdk and then testing with that.  It's not 100% reliable but 
> 9 times out of 10 I don't get past the grub loader with this patch applied.

This bug?  I did test cow, vmdk and vpc and can't reproduce it.  By
inspection I can find a use after free in bdrv_aio_bh_cb, though.

Will repost the whole series, the win32 aio removal and some
recent scsi-disk commits caused a whole lot of rejects..