From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famcool@gmail.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, hch@lst.de
Subject: Re: [Qemu-devel] [PATCH v6 09/12] VMDK: open/read/write for monolithicFlat image
Date: Fri, 1 Jul 2011 06:23:19 +0100 [thread overview]
Message-ID: <BANLkTim-kgw79=RWfmVWSOuePynGGZvBdA@mail.gmail.com> (raw)
In-Reply-To: <1309496142-14228-10-git-send-email-famcool@gmail.com>
On Fri, Jul 1, 2011 at 5:55 AM, Fam Zheng <famcool@gmail.com> wrote:
> + /* save to extents array */
> + if (!strcmp(type, "FLAT")) {
> + /* FLAT extent */
> + char extent_path[PATH_MAX];
> + BlockDriverState *extent_file;
> + BlockDriver *drv;
> + VmdkExtent *extent;
> +
> + extent_file = bdrv_new("");
> + drv = bdrv_find_format("file");
> + if (!drv) {
> + bdrv_delete(extent_file);
> + return -EINVAL;
> + }
> + path_combine(extent_path, sizeof(extent_path),
> + desc_file_path, fname);
> + ret = bdrv_open(extent_file, extent_path,
> + bs->open_flags | BDRV_O_RDWR | BDRV_O_NO_BACKING, drv);
Why are you forcing BDRV_O_RDWR and BDRV_O_NO_BACKING? It should be
possible to open a vmdk file readonly.
By the way, you can shortcut the bdrv_find_format()/bdrv_open() using
bdrv_open_file(). That will simplify things a little.
BDRV_O_NO_BACKING is not needed with the "file" driver (which doesn't
support backing files).
Stefan
next prev parent reply other threads:[~2011-07-01 5:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 4:55 [Qemu-devel] [PATCH v6 00/12] Adding VMDK monolithic flat support Fam Zheng
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 01/12] VMDK: introduce VmdkExtent Fam Zheng
2011-07-01 12:28 ` Kevin Wolf
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 02/12] VMDK: bugfix, align offset to cluster in get_whole_cluster Fam Zheng
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 03/12] VMDK: probe for monolithicFlat images Fam Zheng
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 04/12] VMDK: separate vmdk_open by format version Fam Zheng
2011-07-01 13:02 ` Kevin Wolf
2011-07-01 13:06 ` Fam Zheng
2011-07-01 13:13 ` Kevin Wolf
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 05/12] VMDK: add field BDRVVmdkState.desc_offset Fam Zheng
2011-07-01 13:08 ` Kevin Wolf
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 06/12] VMDK: flush multiple extents Fam Zheng
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 07/12] VMDK: move 'static' cid_update flag to bs field Fam Zheng
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 08/12] VMDK: change get_cluster_offset return type Fam Zheng
2011-07-01 16:40 ` Kevin Wolf
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 09/12] VMDK: open/read/write for monolithicFlat image Fam Zheng
2011-07-01 5:23 ` Stefan Hajnoczi [this message]
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 10/12] VMDK: create different subformats Fam Zheng
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 11/12] VMDK: fix coding style Fam Zheng
2011-07-01 4:55 ` [Qemu-devel] [PATCH v6 12/12] block: add bdrv_get_allocated_file_size() operation Fam Zheng
2011-07-01 5:25 ` [Qemu-devel] [PATCH v6 00/12] Adding VMDK monolithic flat support 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='BANLkTim-kgw79=RWfmVWSOuePynGGZvBdA@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).