From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: stefanha@gmail.com, Xu Wang <cngesaint@gmail.com>,
qemu-devel@nongnu.org, xiawenc@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH V2 0/5] Add infinite loop check for backing file chain
Date: Wed, 10 Jul 2013 13:42:50 +0200 [thread overview]
Message-ID: <20130710114250.GM3898@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20130710111303.GG18465@T430s.nay.redhat.com>
Am 10.07.2013 um 13:13 hat Fam Zheng geschrieben:
> On Mon, 07/08 03:26, Xu Wang wrote:
> > Updates:
> > 1. Changed infinite loop check in collect_image_info_list() from filename
> > checking to inode checking.
> > 2. Absolute or relative path is OK for filename path.
> > 3. Hard and soft link are works well.
> > 4. Added WIN32 platform support (shortcuts could be recognized correctly.)
> > 5. Create a file which contains loop in backing file will failed.
> > 6. Start a vm which boot block file contains loop in backing file chain
> > will failed instead of no response and segment fault.
> >
> > Xu Wang (5):
> > Refine and export infinite loop checking in collect_image_info_list()
> > Add WIN32 platform support for backing_file_loop_check()
> > Check infinite loop in bdrv_img_create()
> > Add backing file loop check in change_backing_file()
> > Add infinite loop check in drive_init()
> >
> > block.c | 211 ++++++++++++++++++++++++++++++++++++++++++++++++--
> > blockdev.c | 5 ++
> > include/block/block.h | 4 +
> > qemu-img.c | 30 +++----
> > 4 files changed, 224 insertions(+), 26 deletions(-)
> >
>
> Thanks for the series. I made a few comments on each patch. You hashed
> windows full path to get the "inode", but case sensitively, would that
> work with the same files of different case?
I seem to remember that Windows can be made case-sensitive. In this
case, we must not ignore case. Not detecting some loops is okay (but here
we would in fact detect it in the second iteration), rejecting valid
configurations is not.
Kevin
next prev parent reply other threads:[~2013-07-10 11:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 7:26 [Qemu-devel] [PATCH V2 0/5] Add infinite loop check for backing file chain Xu Wang
2013-07-08 7:26 ` [Qemu-devel] [PATCH V2 1/5] Refine and export infinite loop checking in collect_image_info_list() Xu Wang
2013-07-10 10:25 ` Fam Zheng
2013-07-10 10:49 ` Fam Zheng
2013-07-12 2:58 ` Xu Wang
2013-07-08 7:26 ` [Qemu-devel] [PATCH V2 2/5] Add WIN32 platform support for backing_file_loop_check() Xu Wang
2013-07-10 10:44 ` Fam Zheng
2013-07-15 6:09 ` Xu Wang
2013-07-15 6:30 ` Fam Zheng
2013-07-08 7:26 ` [Qemu-devel] [PATCH V2 3/5] Check infinite loop in bdrv_img_create() Xu Wang
2013-07-10 10:52 ` Fam Zheng
2013-07-08 7:26 ` [Qemu-devel] [PATCH V2 4/5] Add backing file loop check in change_backing_file() Xu Wang
2013-07-10 10:57 ` Fam Zheng
2013-07-08 7:26 ` [Qemu-devel] [PATCH V2 5/5] Add infinite loop check in drive_init() Xu Wang
2013-07-10 11:00 ` Fam Zheng
2013-07-10 11:13 ` [Qemu-devel] [PATCH V2 0/5] Add infinite loop check for backing file chain Fam Zheng
2013-07-10 11:42 ` Kevin Wolf [this message]
2013-07-10 17:20 ` 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=20130710114250.GM3898@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=cngesaint@gmail.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).