| commit | afa328b1b25a624517d0c7c461571c49c6ffcf63 | |
| author | Kevin Wolf <kwolf@redhat.com> | |
| Wed, 20 Jan 2010 14:03:05 +0000 (20 15:03 +0100) | ||
| committer | Anthony Liguori <aliguori@us.ibm.com> | |
| Wed, 27 Jan 2010 13:52:32 +0000 (27 07:52 -0600) | ||
| tree | 08e9425226cedb22bb2c0b448ac9dc2043b3099f | treesnapshot (tar.gz zip) |
| parent | 868dab5dc2aeccfd025c3c4712c0124877a704c3 | commitdiff |
qcow2: Allow updating no refcounts
There's absolutely no problem with updating the refcounts of 0 clusters.
At least snapshot code is doing this and would fail once the result of
update_refcount isn't ignored any more.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
(cherry picked from commit 7322afe7eaa7211285a38ccfb754a0a52911e394)
There's absolutely no problem with updating the refcounts of 0 clusters.
At least snapshot code is doing this and would fail once the result of
update_refcount isn't ignored any more.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
(cherry picked from commit 7322afe7eaa7211285a38ccfb754a0a52911e394)
| block/qcow2-refcount.c | diffblobblamehistory |