From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] Consider werror/rerror on immediate bdrv_aio_* failure
Date: Wed, 27 Oct 2010 13:20:51 +0200 [thread overview]
Message-ID: <1288178454-8893-1-git-send-email-kwolf@redhat.com> (raw)
There are still paths where werror/rerror is ignored and an error is directly
communicated to the guest. This series fixes some of them.
Kevin Wolf (3):
ide: Handle immediate bdrv_aio_flush failure
virtio-blk: Handle immediate flush failure properly
scsi-disk: Fix immediate failure of bdrv_aio_*
hw/ide/core.c | 12 +++++++++---
hw/scsi-disk.c | 11 ++++++-----
hw/virtio-blk.c | 2 +-
3 files changed, 16 insertions(+), 9 deletions(-)
--
1.7.2.3
next reply other threads:[~2010-10-27 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 11:20 Kevin Wolf [this message]
2010-10-27 11:20 ` [Qemu-devel] [PATCH 1/3] ide: Handle immediate bdrv_aio_flush failure Kevin Wolf
2010-10-27 11:20 ` [Qemu-devel] [PATCH 2/3] virtio-blk: Handle immediate flush failure properly Kevin Wolf
2010-10-27 11:20 ` [Qemu-devel] [PATCH 3/3] scsi-disk: Fix immediate failure of bdrv_aio_* Kevin Wolf
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=1288178454-8893-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).