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 6/6] block: Add infinite loop check in drive_init()
Date: Fri, 02 Aug 2013 16:33:33 -0600 [thread overview]
Message-ID: <51FC33BD.8010309@redhat.com> (raw)
In-Reply-To: <1375434137-4452-7-git-send-email-gesaint@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
On 08/02/2013 03:02 AM, Xu Wang wrote:
> From: Xu Wang <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
s/Becase/Because/
> and segment fault occured. So this patch would check backing file
s/occured/occurred/
> chain if there is loop in it before open image.
I'd suggest:
Check the backing file for a loop during image boot, to avoid a lack or
response or segfault.
>
> Signed-off-by: Xu Wang <cngesaint@gmail.com>
> ---
> blockdev.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/blockdev.c b/blockdev.c
> index b3a57e0..590193f 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -695,6 +695,13 @@ 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)) {
> + error_report("drive_init: backing file loop check failed!");
The '!' seems a bit of overkill; it is sufficient to give an error
message without trailing punctuation.
> + goto err;
> + }
> +
> ret = bdrv_open(dinfo->bdrv, file, bs_opts, bdrv_flags, drv);
> bs_opts = NULL;
>
>
--
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 --]
prev parent reply other threads:[~2013-08-02 22:33 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
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 [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=51FC33BD.8010309@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 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).