From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, famz@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] Fix incomplete aio_preadv byte conversion in mirroring
Date: Mon, 13 Jun 2016 12:56:33 -0600 [thread overview]
Message-ID: <1465844195-25911-1-git-send-email-eblake@redhat.com> (raw)
v2: Split the bug fix from the addition of assertions, add a
BDRV_REQ_MASK constant [famz], stick assertions at the more
common entry points
Eric Blake (2):
block: Avoid bogus flags during mirroring
block: Assert that flags are in range
include/block/block.h | 3 +++
block/io.c | 6 ++++++
block/mirror.c | 6 ++----
3 files changed, 11 insertions(+), 4 deletions(-)
--
2.5.5
next reply other threads:[~2016-06-13 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 18:56 Eric Blake [this message]
2016-06-13 18:56 ` [Qemu-devel] [PATCH v2 1/2] block: Avoid bogus flags during mirroring Eric Blake
2016-06-13 18:56 ` [Qemu-devel] [PATCH v2 2/2] block: Assert that flags are in range Eric Blake
2016-06-14 9:11 ` Stefan Hajnoczi
2016-06-14 9:50 ` [Qemu-devel] [PATCH v2 0/2] Fix incomplete aio_preadv byte conversion in mirroring 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=1465844195-25911-1-git-send-email-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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).