From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Jeff Cody <jcody@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
pbonzini@redhat.com, jsnow@redhat.com, wangxiaolong@ucloud.cn
Subject: [Qemu-devel] [PATCH v3 0/6] block: Mirror discarded sectors
Date: Tue, 12 May 2015 19:48:29 +0800 [thread overview]
Message-ID: <1431431315-32079-1-git-send-email-famz@redhat.com> (raw)
v3: Add John's rev-by in patches 3~6.
Rewrite patch 1: discard may not suffice, use write zeroes in that case.
v2: Fix typo and add Eric's rev-by in patch 3.
Add patch 1 to discard target in mirror job. (Paolo)
Add patch 6 to improve iotests.wait_ready. (John)
This fixes the mirror assert failure reported by wangxiaolong:
https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg04458.html
The direct cause is that hbitmap code couldn't handle unset of bits *after*
iterator's current position. We could fix that, but the bdrv_reset_dirty() call
is more questionable:
Before, if guest discarded some sectors during migration, it could see
different data after moving to dest side, depending on block backends of the
src and the dest. This is IMO worse than mirroring the actual reading as done
in this series, because we don't know what the guest is doing.
For example if a guest first issues WRITE SAME to wipe out the area then issues
UNMAP to discard it, just to get rid of some sensitive data completely, we may
miss both operations and leave stale data on dest image.
Fam Zheng (6):
mirror: Do zero write on target if sectors not allocated
block: Fix dirty bitmap in bdrv_co_discard
block: Remove bdrv_reset_dirty
qemu-iotests: Make block job methods common
qemu-iotests: Add test case for mirror with unmap
iotests: Use event_wait in wait_ready
block.c | 12 --------
block/io.c | 4 +--
block/mirror.c | 53 ++++++++++++++++++++++++++++++----
include/block/block_int.h | 2 --
tests/qemu-iotests/041 | 66 ++++++++++---------------------------------
tests/qemu-iotests/131 | 59 ++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/131.out | 5 ++++
tests/qemu-iotests/group | 1 +
tests/qemu-iotests/iotests.py | 23 +++++++++++++++
9 files changed, 152 insertions(+), 73 deletions(-)
create mode 100644 tests/qemu-iotests/131
create mode 100644 tests/qemu-iotests/131.out
--
2.4.0
next reply other threads:[~2015-05-12 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 11:48 Fam Zheng [this message]
2015-05-12 11:48 ` [Qemu-devel] [PATCH v3 1/6] mirror: Do zero write on target if sectors not allocated Fam Zheng
2015-05-14 10:30 ` Paolo Bonzini
2015-05-14 13:52 ` Fam Zheng
2015-05-12 11:48 ` [Qemu-devel] [PATCH v3 2/6] block: Fix dirty bitmap in bdrv_co_discard Fam Zheng
2015-05-14 10:31 ` Paolo Bonzini
2015-05-12 11:48 ` [Qemu-devel] [PATCH v3 3/6] block: Remove bdrv_reset_dirty Fam Zheng
2015-05-12 11:48 ` [Qemu-devel] [PATCH v3 4/6] qemu-iotests: Make block job methods common Fam Zheng
2015-05-14 10:31 ` Paolo Bonzini
2015-05-12 11:48 ` [Qemu-devel] [PATCH v3 5/6] qemu-iotests: Add test case for mirror with unmap Fam Zheng
2015-05-14 10:37 ` Paolo Bonzini
2015-05-14 13:50 ` Fam Zheng
2015-05-12 11:48 ` [Qemu-devel] [PATCH v3 6/6] iotests: Use event_wait in wait_ready Fam Zheng
2015-05-14 6:27 ` [Qemu-devel] [PATCH v3 0/6] block: Mirror discarded sectors Fam Zheng
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=1431431315-32079-1-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wangxiaolong@ucloud.cn \
/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).