From: Xu Wang <cngesaint@gmail.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@gmail.com,
wdongxu@linux.vnet.ibm.com, Xu Wang <cngesaint@gmail.com>,
xiawenc@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH V3 5/7] block: Add infinite loop check in drive_init()
Date: Mon, 15 Jul 2013 05:42:34 -0400 [thread overview]
Message-ID: <1373881356-3294-6-git-send-email-cngesaint@gmail.com> (raw)
In-Reply-To: <1373881356-3294-1-git-send-email-cngesaint@gmail.com>
Backing file should be checked if there is a loop in it during image
boot. Becase if there is loop qemu would no response for a long time
and segment fault occured. So this patch would check backing file
chain if there is loop in it before open image.
Signed-off-by: Xu Wang <cngesaint@gmail.com>
---
blockdev.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/blockdev.c b/blockdev.c
index b3a57e0..b5f063f 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -695,6 +695,12 @@ DriveInfo *drive_init(QemuOpts *all_opts, BlockInterfaceType block_default_type)
error_report("warning: disabling copy_on_read on readonly drive");
}
+ /* Add backing file loop check */
+ if (bdrv_backing_file_loop_check(file, drv ? drv->format_name : NULL,
+ NULL, NULL)) {
+ goto err;
+ }
+
ret = bdrv_open(dinfo->bdrv, file, bs_opts, bdrv_flags, drv);
bs_opts = NULL;
--
1.8.1.4
next prev parent reply other threads:[~2013-07-15 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 9:42 [Qemu-devel] [PATCH V3 0/7] Redefine and export backing file loop check Xu Wang
2013-07-15 9:42 ` [Qemu-devel] [PATCH V3 1/7] block/qemu-img: Refine and export infinite loop checking in collect_image_info_list() Xu Wang
2013-07-18 5:11 ` Fam Zheng
2013-07-15 9:42 ` [Qemu-devel] [PATCH V3 2/7] block: Add WIN32 platform support for backing_file_loop_check() Xu Wang
2013-07-18 5:24 ` Fam Zheng
2013-07-15 9:42 ` [Qemu-devel] [PATCH V3 3/7] block: Check infinite loop in bdrv_img_create() Xu Wang
2013-07-15 9:42 ` [Qemu-devel] [PATCH V3 4/7] block: Add backing file loop check in change_backing_file() Xu Wang
2013-07-15 9:42 ` Xu Wang [this message]
2013-07-18 5:27 ` [Qemu-devel] [PATCH V3 5/7] block: Add infinite loop check in drive_init() Fam Zheng
2013-07-15 9:42 ` [Qemu-devel] [PATCH V3 6/7] block: Add backing file loop check in qcow2_change_backing_file() Xu Wang
2013-07-18 5:32 ` Fam Zheng
2013-07-15 9:42 ` [Qemu-devel] [PATCH V3 7/7] block: Add backing file loop check in qed_change_backing_file() Xu Wang
2013-07-18 4:56 ` [Qemu-devel] [PATCH V3 0/7] Redefine and export backing file loop check 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=1373881356-3294-6-git-send-email-cngesaint@gmail.com \
--to=cngesaint@gmail.com \
--cc=famz@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 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).