From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, uobergfe@redhat.com,
stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v2 2.1 0/4] Suppress error action on r/w beyond end
Date: Fri, 4 Jul 2014 15:31:56 +0200 [thread overview]
Message-ID: <1404480720-7485-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.
SCSI does that, but virtio-blk and IDE don't. Fix them. No other
device model supports error actions.
v2:
* PATCH 2: Commit message spelling fix [Fam]
* PATCH 4: New, covering IDE
Markus Armbruster (4):
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
ide: Treat read/write beyond end as invalid
hw/block/virtio-blk.c | 45 +++++++++++++++++++++++++++++----------------
hw/ide/core.c | 28 ++++++++++++++++++++++++++++
2 files changed, 57 insertions(+), 16 deletions(-)
--
1.9.3
next reply other threads:[~2014-07-04 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 13:31 Markus Armbruster [this message]
2014-07-04 13:31 ` [Qemu-devel] [PATCH v2 2.1 1/4] virtio-blk: Factor common checks out of virtio_blk_handle_read/write() Markus Armbruster
2014-07-04 13:31 ` [Qemu-devel] [PATCH v2 2.1 2/4] virtio-blk: Bypass error action and I/O accounting on invalid r/w Markus Armbruster
2014-07-09 13:27 ` Kevin Wolf
2014-07-04 13:31 ` [Qemu-devel] [PATCH v2 2.1 3/4] virtio-blk: Treat read/write beyond end as invalid Markus Armbruster
2014-07-04 13:32 ` [Qemu-devel] [PATCH v2 2.1 4/4] ide: " Markus Armbruster
2014-07-09 13:43 ` Kevin Wolf
2014-07-10 7:56 ` 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=1404480720-7485-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=famz@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).