From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60124) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WsWaE-0007bv-1t for qemu-devel@nongnu.org; Thu, 05 Jun 2014 08:15:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WsWa4-0004pB-V8 for qemu-devel@nongnu.org; Thu, 05 Jun 2014 08:15:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:22954) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WsWa4-0004oK-I6 for qemu-devel@nongnu.org; Thu, 05 Jun 2014 08:15:40 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s55CFdV4015299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 5 Jun 2014 08:15:39 -0400 From: Markus Armbruster Date: Thu, 5 Jun 2014 14:15:33 +0200 Message-Id: <1401970536-18019-1-git-send-email-armbru@redhat.com> Subject: [Qemu-devel] [PATCH 0/3] virtio-blk: Suppress error action on r/w beyond end List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kwolf@redhat.com, uobergfe@redhat.com, stefanha@redhat.com When a device model's I/O operation fails, we execute the error action. This lets layers above QEMU implement thin provisioning, or attempt to correct errors before they reach the guest. But when the I/O operation fails because its invalid, reporting the error to the guest is the only sensible action. This short series does exactly that for virtio-blk. I intend to do the same for IDE and SCSI. Markus Armbruster (3): virtio-blk: Factor common checks out of virtio_blk_handle_read/write() virtio-blk: Bypass error action and I/O accounting on invalid r/w virtio-blk: Treat read/write beyond end as invalid hw/block/virtio-blk.c | 45 +++++++++++++++++++++++++++++---------------- 1 file changed, 29 insertions(+), 16 deletions(-) -- 1.9.3