All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: Changlong Xie <xiecl.fnst@cn.fujitsu.com>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Emit QUORUM_REPORT_BAD for reads in fifo mode
Date: Wed, 16 Mar 2016 16:21:50 +0100	[thread overview]
Message-ID: <56E97A0E.4020908@redhat.com> (raw)
In-Reply-To: <cover.1458034554.git.berto@igalia.com>


[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]

On 15.03.2016 10:41, Alberto Garcia wrote:
> This is a follow-up to the "Separate QUORUM_REPORT_BAD events" series:
> 
>    https://lists.gnu.org/archive/html/qemu-devel/2016-03/msg02402.html
> 
> If there's an I/O error in one of Quorum children then QEMU should
> emit QUORUM_REPORT_BAD. However this is not working with
> read-pattern=fifo. This patch fixes this problem.
> 
> This applies on top of Kevin's block branch.
> 
> Regards,
> 
> Berto
> 
> Alberto Garcia (2):
>   quorum: Emit QUORUM_REPORT_BAD for reads in fifo mode
>   iotests: Test QUORUM_REPORT_BAD in fifo mode
> 
>  block/quorum.c             | 17 +++++++++--------
>  tests/qemu-iotests/148     | 17 +++++++++++++++--
>  tests/qemu-iotests/148.out |  4 ++--
>  3 files changed, 26 insertions(+), 12 deletions(-)

Thanks, applied to my block tree:

https://github.com/XanClic/qemu/commits/block

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      parent reply	other threads:[~2016-03-16 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15  9:41 [Qemu-devel] [PATCH 0/2] Emit QUORUM_REPORT_BAD for reads in fifo mode Alberto Garcia
2016-03-15  9:41 ` [Qemu-devel] [PATCH 1/2] quorum: " Alberto Garcia
2016-03-16 15:08   ` Max Reitz
2016-03-15  9:41 ` [Qemu-devel] [PATCH 2/2] iotests: Test QUORUM_REPORT_BAD " Alberto Garcia
2016-03-16 15:17   ` Max Reitz
2016-03-16 15:21 ` Max Reitz [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=56E97A0E.4020908@redhat.com \
    --to=mreitz@redhat.com \
    --cc=berto@igalia.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=xiecl.fnst@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.