From: Hao QingFeng <haoqf@linux.vnet.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
cornelia.huck@de.ibm.com, borntraeger@de.ibm.com,
famz@redhat.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.8 v1 1/1] block/vmdk: Fix the endian problem of buf_len
Date: Fri, 25 Nov 2016 18:48:28 +0800 [thread overview]
Message-ID: <36ff325c-19f7-80d4-bd5f-d8bf4b1b364e@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161125102121.GB4584@noname.redhat.com>
在 2016-11-25 18:21, Kevin Wolf 写道:
> [ Cc: Fam, qemu-stable ]
>
> Am 25.11.2016 um 11:06 hat QingFeng Hao geschrieben:
>> The problem was triggered by qemu-iotests case 055. It failed when it
>> was comparing the compressed vmdk image with original test.img.
>>
>> The cause is that buf_len in vmdk_write_extent wasn't converted to
>> little-endian before it was stored to disk. But later vmdk_read_extent
>> read it and converted it from little-endian to cpu endian.
>> If the cpu is big-endian like s390, the problem will happen and
>> the data length read by vmdk_read_extent will become invalid!
>> The fix is to add the conversion in vmdk_write_extent.
>>
>> Signed-off-by: QingFeng Hao <haoqf@linux.vnet.ibm.com>
>> Signed-off-by: Jing Liu <liujbjl@linux.vnet.ibm.com>
> Sounds like something that should still be fixed for 2.8 and in the
> stable branches.
I didn't find the stable branch on upstream, the latest is 2.6 maybe
it's a private one? :-)
>
>> diff --git a/block/vmdk.c b/block/vmdk.c
>> index a11c27a..bf6667f 100644
>> --- a/block/vmdk.c
>> +++ b/block/vmdk.c
>> @@ -1355,7 +1355,7 @@ static int vmdk_write_extent(VmdkExtent *extent, int64_t cluster_offset,
>> }
>>
>> data->lba = offset >> BDRV_SECTOR_BITS;
>> - data->size = buf_len;
>> + data->size = cpu_to_le32(buf_len);
> At least data->lba needs to be fixed, too, both here and in
> vmdk_read_extent(). Host endianness in an image file is always wrong.
Good detection!
>
> Maybe we should audit the whole driver for endianness problems.
Good sight! maybe we can encapsulate a suite of endianness functions
for the structures to avoid missing some elements of them like lba?
Also will be better for reuse. When I am checking the endianness calls
in vmdk_create_extent, I am just afraid of missing one. :-)
Thanks!
>
> Kevin
>
--
QingFeng Hao(Robin)
next prev parent reply other threads:[~2016-11-25 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 10:06 [Qemu-devel] [PATCH v1 0/1] qemu: fix the bug reported by qemu-iotests case 055 QingFeng Hao
2016-11-25 10:06 ` [Qemu-devel] [PATCH v1 1/1] block/vmdk: Fix the endian problem of buf_len QingFeng Hao
2016-11-25 10:21 ` [Qemu-devel] [PATCH for-2.8 " Kevin Wolf
2016-11-25 10:48 ` Hao QingFeng [this message]
2016-11-25 12:05 ` Kevin Wolf
2016-11-25 14:00 ` Hao QingFeng
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=36ff325c-19f7-80d4-bd5f-d8bf4b1b364e@linux.vnet.ibm.com \
--to=haoqf@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).