From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MyMml-0002a3-TU
	for qemu-devel@nongnu.org; Thu, 15 Oct 2009 05:38:16 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MyMmg-0002Yj-7C
	for qemu-devel@nongnu.org; Thu, 15 Oct 2009 05:38:14 -0400
Received: from [199.232.76.173] (port=60747 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MyMmf-0002Ye-UF
	for qemu-devel@nongnu.org; Thu, 15 Oct 2009 05:38:10 -0400
Received: from mx1.redhat.com ([209.132.183.28]:42628)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kwolf@redhat.com>) id 1MyMmf-000458-Bu
	for qemu-devel@nongnu.org; Thu, 15 Oct 2009 05:38:09 -0400
Received: from int-mx08.intmail.prod.int.phx2.redhat.com
	(int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9F9c7k1014010
	for <qemu-devel@nongnu.org>; Thu, 15 Oct 2009 05:38:07 -0400
Message-ID: <4AD6ED3B.1030902@redhat.com>
Date: Thu, 15 Oct 2009 11:36:59 +0200
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] Pass the drive's readonly attribute to the
	guest OS
References: <4AD5F3BD.2040402@redhat.com> <4AD5FEF2.2000308@redhat.com>
In-Reply-To: <4AD5FEF2.2000308@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Naphtali Sprei <nsprei@redhat.com>
Cc: qemu-devel@nongnu.org

Am 14.10.2009 18:40, schrieb Naphtali Sprei:
> Naphtali Sprei wrote:
> <snip>
>> I'm planning to investigate where qemu should check the read only attribute before exeuting any write command
>> to drives, would be sent in a different patch.
> 
> revisiting it, if guest OS knows it's a read only device and tries to modify it, anyhow, we don't really care about error reporting,
> as long as qemu doesn't crash (or modify the drive).

If the right response to a write on a read-only device is defined in the
specification (and it most probably is), we should still give the right
response, even though the OS is doing something wrong.

Kevin