From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famcool@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH 03/12] VMDK: probe for mono flat image
Date: Wed, 15 Jun 2011 06:31:14 +0100 [thread overview]
Message-ID: <BANLkTikvwKo8jRw6_i5iFE8kXmgv6UAhvA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTingL_Xme5ywtPEPahxTaMyJhnQX7A@mail.gmail.com>
On Wed, Jun 15, 2011 at 5:26 AM, Fam Zheng <famcool@gmail.com> wrote:
> On Tue, Jun 14, 2011 at 4:06 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> On Sat, Jun 04, 2011 at 08:40:50AM +0800, Fam Zheng wrote:
>>> vmdk_probe for mono flat images.
>>>
>>> Signed-off-by: Fam Zheng <famcool@gmail.com>
>>> ---
>>> block/vmdk.c | 13 ++++++++++---
>>> 1 files changed, 10 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/block/vmdk.c b/block/vmdk.c
>>> index f787528..bf8d02a 100644
>>> --- a/block/vmdk.c
>>> +++ b/block/vmdk.c
>>> @@ -101,10 +101,17 @@ static int vmdk_probe(const uint8_t *buf, int
>>> buf_size, const char *filename)
>>> return 0;
>>> magic = be32_to_cpu(*(uint32_t *)buf);
>>> if (magic == VMDK3_MAGIC ||
>>> - magic == VMDK4_MAGIC)
>>> + magic == VMDK4_MAGIC) {
>>> return 100;
>>> - else
>>> - return 0;
>>> + } else {
>>> + char *cid_p, *ct_p, *extent_p;
>>> + cid_p = strstr((char *)buf, "CID");
>>> + ct_p = strstr((char *)buf, "createType");
>>> + extent_p = strstr((char *)buf, "RW");
>>> + if (cid_p && ct_p && extent_p)
>>> + return 100;
>>
>> NUL-terminated string functions cannot be used for probing because the
>> input file may be invalid. If the magic number matches but there is no
>> NUL in the buffer then the strstr(3) will run off the end of the buffer.
>>
>> Also note that the specification says "The descriptor file is not
>> case-sensitive". "cid", "CiD", and "CID" should all be allowed.
>>
>> Do non-monolithic vmdk images always have "# Disk DescriptorFile" as the
>> first line? Perhaps you can test for that using memcmp(3) instead.
> No guarantee in specification, although VMware does start descriptors
> with such a line "# Disk DescriptorFile".
> But is it proper that we make this assumption?
Have you tried removing that comment line to see if VMware still
recognizes the file?
Stefan
next prev parent reply other threads:[~2011-06-15 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 0:40 [Qemu-devel] [PATCH 03/12] VMDK: probe for mono flat image Fam Zheng
2011-06-14 8:06 ` Stefan Hajnoczi
2011-06-15 4:26 ` Fam Zheng
2011-06-15 5:31 ` Stefan Hajnoczi [this message]
2011-06-15 5:45 ` Fam Zheng
2011-06-15 6:10 ` 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=BANLkTikvwKo8jRw6_i5iFE8kXmgv6UAhvA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=famcool@gmail.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@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).