All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: "Li, Haicheng" <haicheng.li@intel.com>,
	xen-devel@lists.xensource.com,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: VMX status report. Xen: #17630 & Xen0: #540 -- blocked
Date: Thu, 15 May 2008 11:00:43 +0200	[thread overview]
Message-ID: <482BFBBB.6030904@suse.de> (raw)
In-Reply-To: <FF386CB4AE0E4648B0A96060EC00F36CA72200@pdsmsx412.ccr.corp.intel.com>

Xu, Dongxiao schrieb:
> I just looked into this issue, and I was confused by the recursive function call while opening a qcow file (bdrv_open2->qcow_open->bdrv_file_open->bdrv_open2->...).
>     Remove the modification in block.c in C/S 17606 could work around this issue, but it is not a good way.

I think the right solution is to remove bdrv_open altogether and force
the callers to provide the driver as parameter to bdrv_open2. For qcow
itself the following patch could be enough (compiles, but completely
untested).

But then, I don't even understand why find_protocol has been crippled -
isn't this one harmless and we should rather have removed the actual
guessing in find_image_format?

Kevin


diff -r 0beee5c839ea tools/ioemu/block.c
--- a/tools/ioemu/block.c       Tue May 13 12:17:08 2008
+++ b/tools/ioemu/block.c       Thu May 15 11:51:15 2008
@@ -329,7 +329,7 @@
     bs = bdrv_new("");
     if (!bs)
         return -ENOMEM;
-    ret = bdrv_open2(bs, filename, flags | BDRV_O_FILE, NULL);
+    ret = bdrv_open2(bs, filename, flags | BDRV_O_FILE, &bdrv_raw);
     if (ret < 0) {
         bdrv_delete(bs);
         return ret;

  reply	other threads:[~2008-05-15  9:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  9:50 VMX status report. Xen: #17630 & Xen0: #540 -- blocked Li, Haicheng
2008-05-14 10:44 ` Ian Jackson
2008-05-15  7:40   ` Li, Haicheng
2008-05-15  8:30     ` Xu, Dongxiao
2008-05-15  9:00       ` Kevin Wolf [this message]
2008-05-15  9:31         ` Xu, Dongxiao
2008-05-15  9:50           ` Kevin Wolf
2008-05-15 11:07             ` Ian Jackson
2008-05-15 11:54               ` Kevin Wolf
2008-05-15 13:07                 ` Ian Jackson
2008-05-15 13:53                   ` Kevin Wolf
2008-05-16  1:38               ` Xu, Dongxiao
2008-05-16  9:14                 ` Ian Jackson

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=482BFBBB.6030904@suse.de \
    --to=kwolf@suse.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dongxiao.xu@intel.com \
    --cc=haicheng.li@intel.com \
    --cc=xen-devel@lists.xensource.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 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.