From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, eblake@redhat.com,
den@openvz.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] qcow2: write_zeroes corruption fixes and tests
Date: Tue, 17 May 2016 18:51:00 +0200 [thread overview]
Message-ID: <1463503863-19009-1-git-send-email-kwolf@redhat.com> (raw)
These are the qcow2 write_zeroes fixes that need to be merged with the next
pull request as they can actually cause image corruption. The rest of Den's
patches are mostly cleanups, so they aren't quite as urgent.
Denis V. Lunev (1):
qcow2: fix condition in is_zero_cluster
Kevin Wolf (2):
qcow2: Fix write_zeroes with partially allocated backing file cluster
qemu-iotests: Some more write_zeroes tests
block/qcow2.c | 3 +-
tests/qemu-iotests/154 | 100 +++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/154.out | 64 +++++++++++++++++++++++++++++
tests/qemu-iotests/group | 1 +
4 files changed, 167 insertions(+), 1 deletion(-)
create mode 100755 tests/qemu-iotests/154
create mode 100644 tests/qemu-iotests/154.out
--
1.8.3.1
next reply other threads:[~2016-05-17 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 16:51 Kevin Wolf [this message]
2016-05-17 16:51 ` [Qemu-devel] [PATCH 1/3] qcow2: fix condition in is_zero_cluster Kevin Wolf
2016-05-17 17:25 ` Eric Blake
2016-05-17 16:51 ` [Qemu-devel] [PATCH 2/3] qcow2: Fix write_zeroes with partially allocated backing file cluster Kevin Wolf
2016-05-17 17:22 ` Eric Blake
2016-05-17 19:20 ` Denis V. Lunev
2016-05-17 16:51 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: Some more write_zeroes tests Kevin Wolf
2016-05-17 20:35 ` Eric Blake
2016-05-18 10:09 ` Kevin Wolf
2016-05-18 12:27 ` [Qemu-devel] [PATCH v2 " Kevin Wolf
2016-05-18 14:12 ` Eric Blake
2016-05-18 14:22 ` 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=1463503863-19009-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=mreitz@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).