From: Stefan Hajnoczi <stefanha@gmail.com>
To: Xiaodong Gong <gordongong0350@gmail.com>
Cc: kwolf@redhat.com, Xiaodong Gong <gongxiaodong1@huawei.com>,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block:Fix FIXED base vpc be probed to raw format
Date: Mon, 9 Feb 2015 14:54:28 +0000 [thread overview]
Message-ID: <20150209145428.GB2076@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1423399192-8569-1-git-send-email-gongxiaodong1@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Sun, Feb 08, 2015 at 08:39:52PM +0800, Xiaodong Gong wrote:
> When open the vpc snapshot based FIXED format, its backing file,
> this FIXED vpc image, could be probed as a raw image, because that
> the find_image_format just checkout the first sector.
>
> Add a re-probe for the last sector to FIXED base vpc image,when get
> a NULL or raw driver in first sector probe.
>
> Signed-off-by: Xiaodong Gong <gongxiaodong1@huawei.com>
> ---
> block.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 48 insertions(+), 7 deletions(-)
This approach is likely to cause issues because it makes no distiction
between headers and footers. Most image formats only have a header and
would now be misdetected if a raw image had a header in its last sector.
When a vpc image has a backing file, does it make sense to set the
bs->backing_format to "vpc"? That way we'll try to open the backing
file as a vpc image without probing.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-02-09 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 12:39 [Qemu-devel] [PATCH] block:Fix FIXED base vpc be probed to raw format Xiaodong Gong
2015-02-09 14:54 ` Stefan Hajnoczi [this message]
2015-02-10 15:04 ` Xiaodong Gong
2015-02-11 13:39 ` Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2015-02-14 2:13 Xiaodong Gong
2015-02-15 13:41 ` Xiaodong Gong
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=20150209145428.GB2076@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=gongxiaodong1@huawei.com \
--cc=gordongong0350@gmail.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 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).