summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2010-04-21 11:37:52 +0200
committerKevin Wolf <kwolf@redhat.com>2010-05-03 10:07:32 +0200
commit003fad6e2cae5311d3aea996388c90e3ab17de90 (patch)
treef99d05b8e7cd8ed36bca9d01793be2bb9c7cdc87
parentae6b0ed6d4d4a41e77584f44d2888303645fa845 (diff)
downloadqemu-003fad6e2cae5311d3aea996388c90e3ab17de90.tar.gz
qemu-003fad6e2cae5311d3aea996388c90e3ab17de90.tar.bz2
qemu-003fad6e2cae5311d3aea996388c90e3ab17de90.zip
qcow2: Remove abort on free_clusters failure
While it's true that during regular operation free_clusters failure would be a bug, an I/O error can always happen. There's no need to kill the VM, the worst thing that can happen (and it will) is that we leak some clusters. Signed-off-by: Kevin Wolf <kwolf@redhat.com>
-rw-r--r--block/qcow2-refcount.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/block/qcow2-refcount.c b/block/qcow2-refcount.c
index 95491d3388..744107cd1d 100644
--- a/block/qcow2-refcount.c
+++ b/block/qcow2-refcount.c
@@ -638,7 +638,7 @@ void qcow2_free_clusters(BlockDriverState *bs,
ret = update_refcount(bs, offset, size, -1);
if (ret < 0) {
fprintf(stderr, "qcow2_free_clusters failed: %s\n", strerror(-ret));
- abort();
+ /* TODO Remember the clusters to free them later and avoid leaking */
}
}