From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JS5Zz-0004BY-Of
	for qemu-devel@nongnu.org; Thu, 21 Feb 2008 02:10:51 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JS5Zy-00049T-3h
	for qemu-devel@nongnu.org; Thu, 21 Feb 2008 02:10:51 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JS5Zy-00049G-0M
	for qemu-devel@nongnu.org; Thu, 21 Feb 2008 02:10:50 -0500
Received: from an-out-0708.google.com ([209.85.132.243])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <iksiloev@gmail.com>) id 1JS5Zx-0007VO-S0
	for qemu-devel@nongnu.org; Thu, 21 Feb 2008 02:10:50 -0500
Received: by an-out-0708.google.com with SMTP id b38so796736ana.130
	for <qemu-devel@nongnu.org>; Wed, 20 Feb 2008 23:10:48 -0800 (PST)
Message-ID: <9e72fb5d0802202310o72503b88q99170bd96227fba3@mail.gmail.com>
Date: Thu, 21 Feb 2008 08:10:48 +0100
From: "Thomas Irlet" <iksiloev@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] bdrv_flush error handling
In-Reply-To: <200802201355.48502.rickv@hobi.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1594_27778794.1203577848426"
References: <18364.19722.241175.337829@mariner.uk.xensource.com>
	<20080220182252.GH14209@redhat.com> <47BC790D.40409@codemonkey.ws>
	<200802201355.48502.rickv@hobi.com>
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

------=_Part_1594_27778794.1203577848426
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Sometimes the guest intentionally seeks the error. Example?

TrueCrypt 5.0 supports encryption of the full system disk. To get the real
size of the disk, the truecrypt driver queries the number of blocks of the
disk, but then tries to read after the last block, until it gets an error.
Qemu hangs in this operation. So, for me, the blockdriver has to give the
errors back to the guest (in this case, reading behind eof). In no cases,
qemu should die because of that.


Tom

PS: I had to patch truecrypt because of this qemu feature.

------=_Part_1594_27778794.1203577848426
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Sometimes the guest intentionally seeks the error. Example?<br><br>TrueCrypt 5.0 supports encryption of the full system disk. To get the real size of the disk, the truecrypt driver queries the number of blocks of the disk, but then tries to read after the last block, until it gets an error. Qemu hangs in this operation. So, for me, the blockdriver has to give the errors back to the guest (in this case, reading behind eof). In no cases, qemu should die because of that.<br>
<br><br>Tom<br><br>PS: I had to patch truecrypt because of this qemu feature.<br>

------=_Part_1594_27778794.1203577848426--