All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Xu Wang <cngesaint@gmail.com>
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@gmail.com,
	Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org, wdongxu@linux.vnet.ibm.com,
	Xu Wang <gesaint@linux.vnet.ibm.com>,
	xiawenc@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH V6 2/5] qemu-img: Add infinite loop checking in bdrv_new_open()
Date: Fri, 08 Nov 2013 17:27:30 +0100	[thread overview]
Message-ID: <527D10F2.5050606@weilnetz.de> (raw)
In-Reply-To: <20131108161935.GC19612@localhost.localdomain>

See more suggestions below.

Am 08.11.2013 17:19, schrieb Jeff Cody:
> On Tue, Nov 05, 2013 at 10:09:18PM -0500, Xu Wang wrote:
>> Every image should be checked if there is infinite loop in backing
>> file chain before open it. So infinite loop check was added into.

... if there is an infinite loop in the backing
file chain before opening it. ...

>> bdrv_new_open(). If @filename is opened without the flag
>> BDRV_O_NO_BACKING, the infinite loop check should be called.
>>
>> Signed-off-by: Xu Wang <gesaint@linux.vnet.ibm.com>
>> ---
>>  qemu-img.c | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>
>> diff --git a/qemu-img.c b/qemu-img.c
>> index d5ec45b..3af7996 100644
>> --- a/qemu-img.c
>> +++ b/qemu-img.c
>> @@ -281,6 +281,14 @@ static BlockDriverState *bdrv_new_open(const char *filename,
>>          drv = NULL;
>>      }
>>  
>> +    /* check backing file loop if the whole chain need to be opened */

... if the whole chain needs to be opened ...

>> +    if (!(flags & BDRV_O_NO_BACKING) &&
>> +        !bdrv_backing_chain_okay(filename, fmt)) {
>> +        error_report("bdrv_new_open: Open %s failed. There is loop exists "
>> +                     "in the backing chain", filename);
> I suggest rewording this for grammar; something like:
>  +        error_report("bdrv_new_open: Open %s failed. An infinite loop exists "
>  +                     "in the backing chain", filename);
>
>
>> +        goto fail;
>> +    }
>> +
>>      ret = bdrv_open(bs, filename, NULL, flags, drv, &local_err);
>>      if (ret < 0) {
>>          error_report("Could not open '%s': %s", filename,
>> -- 
>> 1.8.1.4

  reply	other threads:[~2013-11-08 16:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06  3:09 [Qemu-devel] [PATCH V6 0/5] Refine and export backing file loop check Xu Wang
2013-11-06  3:09 ` [Qemu-devel] [PATCH V6 1/5] block/qemu-img: Refine and export infinite loop checking in collect_image_info_list() Xu Wang
2013-11-08 10:19   ` Fam Zheng
2013-11-08 13:53     ` Eric Blake
2013-11-08 14:46       ` Jeff Cody
2013-11-06  3:09 ` [Qemu-devel] [PATCH V6 2/5] qemu-img: Add infinite loop checking in bdrv_new_open() Xu Wang
2013-11-08 10:21   ` Fam Zheng
2013-11-08 16:19   ` Jeff Cody
2013-11-08 16:27     ` Stefan Weil [this message]
2013-11-06  3:09 ` [Qemu-devel] [PATCH V6 3/5] block: Add check infinite loop in bdrv_img_create() Xu Wang
2013-11-08 10:22   ` Fam Zheng
2013-11-06  3:09 ` [Qemu-devel] [PATCH V6 4/5] block: Add backing file loop check in change_backing_file() Xu Wang
2013-11-06  3:09 ` [Qemu-devel] [PATCH V6 5/5] blockdev: Add infinite loop check in drive_init() Xu Wang
2013-11-08 10:26   ` Fam Zheng

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=527D10F2.5050606@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=cngesaint@gmail.com \
    --cc=famz@redhat.com \
    --cc=gesaint@linux.vnet.ibm.com \
    --cc=jcody@redhat.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.