qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, jcody@redhat.com,
	Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
	stefanha@redhat.com, mreitz@redhat.com
Subject: [Qemu-devel] [PATCH V7 3/6] qcow2: do not free clusters when fail in header update in qcow2_write_snapshots
Date: Thu,  5 Dec 2013 20:02:49 +0800	[thread overview]
Message-ID: <1386244972-528-4-git-send-email-xiawenc@linux.vnet.ibm.com> (raw)
In-Reply-To: <1386244972-528-1-git-send-email-xiawenc@linux.vnet.ibm.com>

Signed-off-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
---
 block/qcow2-snapshot.c |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/block/qcow2-snapshot.c b/block/qcow2-snapshot.c
index d7ab4ae..55746c4 100644
--- a/block/qcow2-snapshot.c
+++ b/block/qcow2-snapshot.c
@@ -299,6 +299,14 @@ static int qcow2_write_snapshots(BlockDriverState *bs, Error **errp)
                          "Failed in update of image header at %d with size %d",
                          (int)offsetof(QCowHeader, nb_snapshots),
                          (int)sizeof(header_data));
+
+        /*
+         * If the snapshot data part has been updated on disk, then the
+         * clusters at snapshot_offset may be used in next snapshot operation.
+         * If we free those clusters in fail path, they may be allocated and
+         * made dirty causing damage, so skip cluster free to be safe.
+         */
+        snapshots_offset = 0;
         goto fail;
     }
 
-- 
1.7.1

  parent reply	other threads:[~2013-12-05 12:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 12:02 [Qemu-devel] [PATCH V7 0/6] qcow2: rollback the modification on fail in snapshot creation Wenchao Xia
2013-12-05 12:02 ` [Qemu-devel] [PATCH V7 1/6] snapshot: add parameter *errp in snapshot create Wenchao Xia
2013-12-20 14:26   ` Stefan Hajnoczi
2013-12-05 12:02 ` [Qemu-devel] [PATCH V7 2/6] qcow2: add error message in qcow2_write_snapshots() Wenchao Xia
2013-12-20 13:48   ` Stefan Hajnoczi
2013-12-05 12:02 ` Wenchao Xia [this message]
2013-12-05 12:02 ` [Qemu-devel] [PATCH V7 4/6] qcow2: cancel the modification on fail in qcow2_snapshot_create() Wenchao Xia
2013-12-20 14:20   ` Stefan Hajnoczi
2013-12-23  2:57     ` Wenchao Xia
2013-12-23  6:12       ` Wenchao Xia
2014-01-02  3:42         ` Stefan Hajnoczi
2013-12-05 12:02 ` [Qemu-devel] [PATCH V7 5/6] blkdebug: add debug events for snapshot Wenchao Xia
2013-12-05 12:02 ` [Qemu-devel] [PATCH V7 6/6] qemu-iotests: add test for qcow2 snapshot Wenchao Xia
2013-12-09  3:41 ` [Qemu-devel] [PATCH V7 0/6] qcow2: rollback the modification on fail in snapshot creation Wenchao Xia
2013-12-13  2:15 ` Wenchao Xia
2013-12-18  2:13 ` Wenchao Xia
2013-12-18 13:26   ` Stefan Hajnoczi
2013-12-20 14:27 ` Stefan Hajnoczi

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=1386244972-528-4-git-send-email-xiawenc@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).