All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: liujing <liujbjl@linux.vnet.ibm.com>, kwolf@redhat.com
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	borntraeger@de.ibm.com,
	"cornelia.huck@de.ibm.com QingFeng Hao"
	<haoqf@linux.vnet.ibm.com>,
	qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 1/1] block/vmdk: Fix the endian problem of buf_len and lba
Date: Mon, 16 Jan 2017 13:26:00 +0800	[thread overview]
Message-ID: <20170116052600.GA16076@lemon> (raw)
In-Reply-To: <7428bd3f-0cc8-f42f-a2bd-442c2c6ffbef@linux.vnet.ibm.com>

On Mon, 01/16 10:38, liujing wrote:
> Dears,
> 
> We would like to know if this patch will be pulled
> 
> into upstream or what else we need to do for it?
> 
> Because for upstream, the qemu-iotests case 055 still failed.

Kevin, would you like to take this or should I do it?

Fam

> 
> Thanks.
> 
> Jing
> 
> 
> On 12/16/2016 01:20 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>
> > Reviewed-by: Fam Zheng <famz@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) {
> 
> 

  reply	other threads:[~2017-01-16  5:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16  5:20 [Qemu-devel] [PATCH v3 0/1] qemu: fix the bug reported by qemu-iotests case 055 QingFeng Hao
2016-12-16  5:20 ` [Qemu-devel] [PATCH v3 1/1] block/vmdk: Fix the endian problem of buf_len and lba QingFeng Hao
2017-01-16  2:38   ` liujing
2017-01-16  5:26     ` Fam Zheng [this message]
2017-01-23 10:51       ` Fam Zheng
2017-01-25 16:25   ` [Qemu-devel] [Qemu-block] " Max Reitz
2017-02-13  9:17     ` 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=20170116052600.GA16076@lemon \
    --to=famz@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=haoqf@linux.vnet.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 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.