qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dongxu Wang <wdongxu@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [RFC] Check backing_file chain's loop
Date: Fri, 31 May 2013 10:17:48 +0800	[thread overview]
Message-ID: <51A8084C.3010505@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130530124830.GA6169@stefanha-thinkpad.redhat.com>

On 2013/5/30 20:48, Stefan Hajnoczi wrote:
>> hain 1.qcow2' don't crash.
> qemu-img info --backing-chain detects cycles and returns an error, see
> the hash table in collect_image_info_list().
>
> We should protect bdrv_open() too.
>
Okay, will send a patch.
> Stefan
>
>

      reply	other threads:[~2013-05-31  2:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 10:14 [Qemu-devel] [RFC] Check backing_file chain's loop Dongxu Wang
2013-05-30 12:12 ` Eric Blake
2013-05-30 12:48   ` Stefan Hajnoczi
2013-05-31  2:17     ` Dongxu Wang [this message]

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=51A8084C.3010505@linux.vnet.ibm.com \
    --to=wdongxu@linux.vnet.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --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).