From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, uobergfe@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] virtio-blk: Suppress error action on r/w beyond end
Date: Thu, 5 Jun 2014 14:15:33 +0200 [thread overview]
Message-ID: <1401970536-18019-1-git-send-email-armbru@redhat.com> (raw)
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
next reply other threads:[~2014-06-05 12:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 12:15 Markus Armbruster [this message]
2014-06-05 12:15 ` [Qemu-devel] [PATCH 1/3] virtio-blk: Factor common checks out of virtio_blk_handle_read/write() Markus Armbruster
2014-06-06 3:14 ` Fam Zheng
2014-06-05 12:15 ` [Qemu-devel] [PATCH 2/3] virtio-blk: Bypass error action and I/O accounting on invalid r/w Markus Armbruster
2014-06-06 3:18 ` Fam Zheng
2014-06-06 3:22 ` Eric Blake
2014-06-06 6:01 ` Markus Armbruster
2014-06-05 12:15 ` [Qemu-devel] [PATCH 3/3] virtio-blk: Treat read/write beyond end as invalid Markus Armbruster
2014-06-06 3:21 ` Fam Zheng
2014-06-20 4:16 ` Stefan Hajnoczi
2014-06-23 8:47 ` Markus Armbruster
2014-06-23 12:57 ` Markus Armbruster
2014-06-27 9:56 ` Stefan Hajnoczi
2014-06-06 7:36 ` [Qemu-devel] [PATCH 0/3] virtio-blk: Suppress error action on r/w beyond end Paolo Bonzini
2014-06-06 8:24 ` Markus Armbruster
2014-06-26 11:26 ` Markus Armbruster
2014-06-27 9:56 ` Stefan Hajnoczi
2014-07-01 8:57 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1401970536-18019-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=uobergfe@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).