From: Fam Zheng <famz@redhat.com>
To: Xu Wang <cngesaint@gmail.com>
Cc: kwolf@redhat.com, stefanha@gmail.com, wdongxu@linux.vnet.ibm.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V4 4/5] block: Add backing file loop check in change_backing_file()
Date: Mon, 22 Jul 2013 16:50:32 +0800 [thread overview]
Message-ID: <20130722085032.GC8998@T430s.redhat.com> (raw)
In-Reply-To: <1374480349-11412-5-git-send-email-cngesaint@gmail.com>
On Mon, 07/22 04:05, Xu Wang wrote:
> Backing file loop should be checked before calling change_backing_
> file(). If loop appeared, this calling should be stopped and an
> error was printed.
>
> Signed-off-by: Xu Wang <cngesaint@gmail.com>
> ---
> block.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/block.c b/block.c
> index 9daf63c..d996524 100644
> --- a/block.c
> +++ b/block.c
> @@ -1967,6 +1967,13 @@ int bdrv_change_backing_file(BlockDriverState *bs,
> return -EINVAL;
> }
>
> + /* Check if loop exists in backing files chain after changed */
> + if (bdrv_backing_file_loop_check(bs->filename,
> + bs->drv ? bs->drv->format_name : NULL,
> + backing_file, backing_fmt)) {
I'm wondering if it will be helpful to add a concrete error message
here, e.g. for qemu-img rebase, so it will be easier for user to know
it fails because of backing loop.
> + return -EIO;
> + }
> +
> if (drv->bdrv_change_backing_file != NULL) {
> ret = drv->bdrv_change_backing_file(bs, backing_file, backing_fmt);
> } else {
> --
> 1.8.1.4
>
--
Fam
next prev parent reply other threads:[~2013-07-22 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 8:05 [Qemu-devel] [PATCH V4 0/5] Redefine and export backing file loop check Xu Wang
2013-07-22 8:05 ` [Qemu-devel] [PATCH V4 1/5] block/qemu-img: Refine and export infinite loop checking in collect_image_info_list() Xu Wang
2013-07-22 8:05 ` [Qemu-devel] [PATCH V4 2/5] block: Add WIN32 platform support for backing_file_loop_check() Xu Wang
2013-07-22 8:40 ` Fam Zheng
2013-07-22 8:05 ` [Qemu-devel] [PATCH V4 3/5] block: Check infinite loop in bdrv_img_create() Xu Wang
2013-07-22 8:44 ` Fam Zheng
2013-07-22 8:05 ` [Qemu-devel] [PATCH V4 4/5] block: Add backing file loop check in change_backing_file() Xu Wang
2013-07-22 8:50 ` Fam Zheng [this message]
2013-07-22 8:05 ` [Qemu-devel] [PATCH V4 5/5] block: Add infinite loop check in drive_init() Xu Wang
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=20130722085032.GC8998@T430s.redhat.com \
--to=famz@redhat.com \
--cc=cngesaint@gmail.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=wdongxu@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 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).