From: Eric Blake <eblake@redhat.com>
To: Xu Wang <gesaint@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@gmail.com,
qemu-devel@nongnu.org, wdongxu@linux.vnet.ibm.com,
Xu Wang <cngesaint@gmail.com>,
xiawenc@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH V5 2/6] qemu-img: Add infinite loop checking in bdrv_new_open()
Date: Fri, 02 Aug 2013 16:16:13 -0600 [thread overview]
Message-ID: <51FC2FAD.3020402@redhat.com> (raw)
In-Reply-To: <1375434137-4452-3-git-send-email-gesaint@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On 08/02/2013 03:02 AM, Xu Wang wrote:
> From: Xu Wang <cngesaint@gmail.com>
>
> Every image should be checked if there is infinite loop in backing
> file chain before open it. So infinite loop check was added into
> bdrv_new_open(). If @filename is opened with no flags
s/with no flags/without the flag/
> BDRV_O_NO_BACKING, the infinite loop check should be called.
>
> Signed-off-by: Xu Wang <cngesaint@gmail.com>
> ---
> qemu-img.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 4f01b0a..1a63bbf 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -278,6 +278,13 @@ static BlockDriverState *bdrv_new_open(const char *filename,
> drv = NULL;
> }
>
> + /* check backing file loop if the whole chain need to be opened */
> + if (!(flags & BDRV_O_NO_BACKING) &&
> + bdrv_backing_file_loop_check(filename, fmt, NULL, NULL)) {
> + error_report("bdrv_new_open: Open %s failed.", filename);
Error messages generally don't end with '.'; also, this message seems to
lack details that might be useful to the end user (we know that either
the backing chain couldn't be completely followed or has a loop).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-08-02 22:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 9:02 [Qemu-devel] [PATCH V5 0/6] Refine and export backing file loop check Xu Wang
2013-08-02 9:02 ` [Qemu-devel] [PATCH V5 1/6] block/qemu-img: Refine and export infinite loop checking in collect_image_info_list() Xu Wang
2013-08-02 22:09 ` Eric Blake
2013-10-11 8:27 ` Xu Wang
2013-08-02 9:02 ` [Qemu-devel] [PATCH V5 2/6] qemu-img: Add infinite loop checking in bdrv_new_open() Xu Wang
2013-08-02 22:16 ` Eric Blake [this message]
2013-08-02 9:02 ` [Qemu-devel] [PATCH V5 3/6] block: Add WIN32 platform support for backing_file_loop_check() Xu Wang
2013-08-02 22:27 ` Eric Blake
2013-08-02 9:02 ` [Qemu-devel] [PATCH V5 4/6] block: Check infinite loop in bdrv_img_create() Xu Wang
2013-08-02 22:29 ` Eric Blake
2013-08-02 9:02 ` [Qemu-devel] [PATCH V5 5/6] block: Add backing file loop check in change_backing_file() Xu Wang
2013-08-02 22:31 ` Eric Blake
2013-08-02 9:02 ` [Qemu-devel] [PATCH V5 6/6] block: Add infinite loop check in drive_init() Xu Wang
2013-08-02 22:33 ` Eric Blake
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=51FC2FAD.3020402@redhat.com \
--to=eblake@redhat.com \
--cc=cngesaint@gmail.com \
--cc=famz@redhat.com \
--cc=gesaint@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=wdongxu@linux.vnet.ibm.com \
--cc=xiawenc@linux.vnet.ibm.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.