qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xu Wang <gesaint@linux.vnet.ibm.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 V5 0/6] Refine and export backing file loop check
Date: Fri,  2 Aug 2013 05:02:11 -0400	[thread overview]
Message-ID: <1375434137-4452-1-git-send-email-gesaint@linux.vnet.ibm.com> (raw)

From: Xu Wang <cngesaint@gmail.com>

If there is loop exists in the backing file chain, many problems
could be caused by it, such as no response and segment fault during
system boot. Hence stopping backing file loop appear is very necessary.
These patches refine and export loop checking function from collect_image_
info_list() to block.c and build a independent function named bdrv_
backing_file_loop_check(). Backing file loop checking is added before
image created, before change backing file and before system boot.

Updates from V4:
  1. Add backing file loop check in bdrv_new_open().
  2. Adjust open file logic of collect_image_info_list() (bdrv_new_open()
     is called only once when opening the whole chain).
  3. Remove redundant brackets in lnk file check logic.
  4. Add error output in bdrv_img_create().
  5. Remove MAX_PATH_LEN to use PATH_MAX instead.

Updates from V3:
  1. Comments fix for function bdrv_backing_file_loop_check().
  2. Add ret check for fseek()/fread() in get_lnk_target_file().
  3. Add limit of shortcuts filename length reading during comparing.
  4. Add error_report() in driv_init().
  5. Remove redundant loop check in qcow2/qed_change_backing_file().

Updates from V2:
  1. Removed parameter @chain from bdrv_backing_file_loop_check()
  2. Comments and format fix, all patches were checked by checkpatch.pl
  3. Fixed *bs leak.
  4. Improved logic of .lnk file recognization.
  5. Add filename lenth limit check in while()
  6. Changed get_win_inode() to get_inode() and move all inode get method
     into it to make logic more simpler.
  7. Added value of @fmt as suggested.
  8. Added backing file loop check in qcow2.c/qed.c

Xu Wang (6):
  block/qemu-img: Refine and export infinite loop checking in
    collect_image_info_list()
  qemu-img: Add infinite loop checking in bdrv_new_open()
  block: Add WIN32 platform support for backing_file_loop_check()
  block: Check infinite loop in bdrv_img_create()
  block: Add backing file loop check in change_backing_file()
  block: Add infinite loop check in drive_init()

 block.c               | 253 +++++++++++++++++++++++++++++++++++++++++++++++++-
 blockdev.c            |   7 ++
 include/block/block.h |   4 +
 qemu-img.c            |  51 +++++-----
 4 files changed, 284 insertions(+), 31 deletions(-)

-- 
1.8.1.4

             reply	other threads:[~2013-08-02  9:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  9:02 Xu Wang [this message]
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

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=1375434137-4452-1-git-send-email-gesaint@linux.vnet.ibm.com \
    --to=gesaint@linux.vnet.ibm.com \
    --cc=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).