qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hao QingFeng <haoqf@linux.vnet.ibm.com>
To: liujing <liujbjl@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: borntraeger@de.ibm.com, cornelia.huck@de.ibm.com,
	kwolf@redhat.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/1] block/vmdk: Fix the endian problem of buf_len and lba
Date: Mon, 28 Nov 2016 16:11:29 +0800	[thread overview]
Message-ID: <c9049581-6ebb-c65f-ae9b-f9cac2356fa9@linux.vnet.ibm.com> (raw)
In-Reply-To: <c7bc474d-b17f-3530-b1b4-e1c9e66489fb@linux.vnet.ibm.com>



在 2016-11-28 15:56, liujing 写道:
> Hi QingFeng,
>
>
> I just have a question that whether the marker->data
> need convert?
>
> I've no idea, just suddenly realized this question.
>
nope, the data is type of char * for the compressed data stream, so no 
endian issue.
thanks.
> Jing
>
> On 11/26/2016 01:46 PM, QingFeng Hao wrote:
>> 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, meanwhile,
>> repair the endianness problem of lba field which shall also be converted
>> to little-endian before storing to disk.
>>
>> Cc: qemu-stable@nongnu.org
>> Signed-off-by: QingFeng Hao <haoqf@linux.vnet.ibm.com>
>> Signed-off-by: Jing Liu <liujbjl@linux.vnet.ibm.com>
>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>> ---
>>   block/vmdk.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/block/vmdk.c b/block/vmdk.c
>> index a11c27a..26e5f95 100644
>> --- a/block/vmdk.c
>> +++ b/block/vmdk.c
>> @@ -1354,8 +1354,8 @@ static int vmdk_write_extent(VmdkExtent 
>> *extent, int64_t cluster_offset,
>>               goto out;
>>           }
>>
>> -        data->lba = offset >> BDRV_SECTOR_BITS;
>> -        data->size = buf_len;
>> +        data->lba = cpu_to_le64(offset >> BDRV_SECTOR_BITS);
>> +        data->size = cpu_to_le32(buf_len);
>>
>>           n_bytes = buf_len + sizeof(VmdkGrainMarker);
>>           iov = (struct iovec) {
>

-- 
QingFeng Hao(Robin)

  reply	other threads:[~2016-11-28  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26  5:46 [Qemu-devel] [PATCH v2 0/1] qemu: fix the bug reported by qemu-iotests case 055 QingFeng Hao
2016-11-26  5:46 ` [Qemu-devel] [PATCH v2 1/1] block/vmdk: Fix the endian problem of buf_len and lba QingFeng Hao
2016-11-26 11:46   ` [Qemu-devel] [Qemu-stable] " Fam Zheng
2016-11-28  1:51     ` Hao QingFeng
2016-11-28  7:56   ` [Qemu-devel] " liujing
2016-11-28  8:11     ` Hao QingFeng [this message]
2016-11-26  5:51 ` [Qemu-devel] [PATCH v2 0/1] qemu: fix the bug reported by qemu-iotests case 055 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=c9049581-6ebb-c65f-ae9b-f9cac2356fa9@linux.vnet.ibm.com \
    --to=haoqf@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=liujbjl@linux.vnet.ibm.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).