qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: famz@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
	uobergfe@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 2.1 0/4] Suppress error action on r/w beyond end
Date: Thu, 10 Jul 2014 12:27:00 +0200	[thread overview]
Message-ID: <20140710102700.GC3919@noname.redhat.com> (raw)
In-Reply-To: <1404925652-17986-1-git-send-email-armbru@redhat.com>

Am 09.07.2014 um 19:07 hat Markus Armbruster geschrieben:
> 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.

Thanks, applied to the block branch.

Kevin

      parent reply	other threads:[~2014-07-10 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 17:07 [Qemu-devel] [PATCH v4 2.1 0/4] Suppress error action on r/w beyond end Markus Armbruster
2014-07-09 17:07 ` [Qemu-devel] [PATCH v4 2.1 1/4] virtio-blk: Factor common checks out of virtio_blk_handle_read/write() Markus Armbruster
2014-07-09 17:07 ` [Qemu-devel] [PATCH v4 2.1 2/4] virtio-blk: Bypass error action and I/O accounting on invalid r/w Markus Armbruster
2014-07-09 17:07 ` [Qemu-devel] [PATCH v4 2.1 3/4] virtio-blk: Treat read/write beyond end as invalid Markus Armbruster
2014-07-09 17:07 ` [Qemu-devel] [PATCH v4 2.1 4/4] ide: " Markus Armbruster
2014-07-10 10:27 ` Kevin Wolf [this message]

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=20140710102700.GC3919@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=famz@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).