From: Fam Zheng <famcool@gmail.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Fam Zheng <famcool@gmail.com>,
hch@lst.de, stefanha@gmail.com
Subject: [Qemu-devel] [PATCH v3 02/12] VMDK: bugfix, align offset to cluster in get_whole_cluster
Date: Mon, 27 Jun 2011 11:48:28 +0800 [thread overview]
Message-ID: <1309146518-8998-3-git-send-email-famcool@gmail.com> (raw)
In-Reply-To: <1309146518-8998-1-git-send-email-famcool@gmail.com>
In get_whole_cluster, the offset is not aligned to cluster when reading
from backing_hd. When the first write to child is not at the cluster
boundary, wrong address data from parent is copied to child.
Signed-off-by: Fam Zheng <famcool@gmail.com>
---
block/vmdk.c | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/block/vmdk.c b/block/vmdk.c
index c7246f0..0540ec5 100644
--- a/block/vmdk.c
+++ b/block/vmdk.c
@@ -485,21 +485,23 @@ static int get_whole_cluster(BlockDriverState *bs,
/* 128 sectors * 512 bytes each = grain size 64KB */
uint8_t whole_grain[extent->cluster_sectors * 512];
- // we will be here if it's first write on non-exist grain(cluster).
- // try to read from parent image, if exist
+ /* we will be here if it's first write on non-exist grain(cluster).
+ * try to read from parent image, if exist */
if (bs->backing_hd) {
int ret;
if (!vmdk_is_cid_valid(bs))
return -1;
+ /* floor offset to cluster */
+ offset -= offset % (extent->cluster_sectors * 512);
ret = bdrv_read(bs->backing_hd, offset >> 9, whole_grain,
extent->cluster_sectors);
if (ret < 0) {
return -1;
}
- //Write grain only into the active image
+ /* Write grain only into the active image */
ret = bdrv_write(extent->file, cluster_offset, whole_grain,
extent->cluster_sectors);
if (ret < 0) {
next prev parent reply other threads:[~2011-06-27 3:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 3:48 [Qemu-devel] [PATCH v3 00/12] Adding VMDK monolithic flat support Fam Zheng
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 01/12] VMDK: introduce VmdkExtent Fam Zheng
2011-06-27 3:48 ` Fam Zheng [this message]
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 03/12] VMDK: probe for monolithicFlat images Fam Zheng
2011-06-27 4:43 ` Stefan Hajnoczi
2011-06-27 5:11 ` Fam Zheng
2011-06-27 5:33 ` Stefan Hajnoczi
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 04/12] VMDK: separate vmdk_open by format version Fam Zheng
2011-06-27 4:51 ` Stefan Hajnoczi
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 05/12] VMDK: add field BDRVVmdkState.desc_offset Fam Zheng
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 06/12] VMDK: flush multiple extents Fam Zheng
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 07/12] VMDK: move 'static' cid_update flag to bs field Fam Zheng
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 08/12] VMDK: change get_cluster_offset return type Fam Zheng
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 09/12] VMDK: open/read/write for monolithicFlat image Fam Zheng
2011-06-27 4:54 ` Stefan Hajnoczi
2011-06-27 7:00 ` Fam Zheng
2011-06-27 8:10 ` Stefan Hajnoczi
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 10/12] VMDK: create different subformats Fam Zheng
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 11/12] VMDK: fix coding style Fam Zheng
2011-06-27 3:48 ` [Qemu-devel] [PATCH v3 12/12] BlockDriver: add bdrv_get_allocated_file_size() operation 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=1309146518-8998-3-git-send-email-famcool@gmail.com \
--to=famcool@gmail.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).