From: Peter Lieven <pl@kamp.de>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Peter Lieven <pl@kamp.de>,
Fam Zheng <famz@redhat.com>,
stefanha@redhat.com
Subject: [Qemu-devel] [PATCH] block/vmdk: do not report file offset for compressed extents
Date: Thu, 27 Feb 2014 11:15:22 +0100 [thread overview]
Message-ID: <530F103A.7090705@kamp.de> (raw)
Signed-off-by: Peter Lieven <pl@kamp.de>
---
block/vmdk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/vmdk.c b/block/vmdk.c
index ff6f5ee..5fa29b0 100644
--- a/block/vmdk.c
+++ b/block/vmdk.c
@@ -1146,7 +1146,7 @@ static int64_t coroutine_fn vmdk_co_get_block_status(BlockDriverState *bs,
break;
case VMDK_OK:
ret = BDRV_BLOCK_DATA;
- if (extent->file == bs->file) {
+ if (extent->file == bs->file && !extent->compressed) {
ret |= BDRV_BLOCK_OFFSET_VALID | offset;
}
--
1.7.9.5
next reply other threads:[~2014-02-27 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 10:15 Peter Lieven [this message]
2014-02-28 10:30 ` [Qemu-devel] [PATCH] block/vmdk: do not report file offset for compressed extents Stefan Hajnoczi
[not found] <1393408077-556-1-git-send-email-pl@kamp.de>
2014-02-26 10:17 ` Fam Zheng
2014-02-27 10:06 ` Stefan Hajnoczi
2014-02-27 10:15 ` Peter Lieven
2014-02-27 15:49 ` Stefan Hajnoczi
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=530F103A.7090705@kamp.de \
--to=pl@kamp.de \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.