| commit | 791fff504cad4d935dfaab6333ff9b7d95cbfe3f | |
| author | Max Reitz <mreitz@redhat.com> | |
| Fri, 10 Nov 2017 20:31:07 +0000 (10 21:31 +0100) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Fri, 17 Nov 2017 17:21:30 +0000 (17 18:21 +0100) | ||
| tree | 34b0d8dad955aad47c2a6882bbed8a045feaa1a8 | treesnapshot (tar.gz zip) |
| parent | 3e3b838ffeba42eced87595b0a23dc38f7c0c21b | commitdiff |
qcow2: check_errors are fatal
When trying to repair a dirty image, qcow2_check() may apparently
succeed (no really fatal error occurred that would prevent the check
from continuing), but if check_errors in the result object is non-zero,
we cannot trust the image to be usable.
Reported-by: R. Nageswara Sastry <nasastry@in.ibm.com>
Buglink: https://bugs.launchpad.net/qemu/+bug/1728639
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-id: 20171110203111.7666-2-mreitz@redhat.com
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
When trying to repair a dirty image, qcow2_check() may apparently
succeed (no really fatal error occurred that would prevent the check
from continuing), but if check_errors in the result object is non-zero,
we cannot trust the image to be usable.
Reported-by: R. Nageswara Sastry <nasastry@in.ibm.com>
Buglink: https://bugs.launchpad.net/qemu/+bug/1728639
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-id: 20171110203111.7666-2-mreitz@redhat.com
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
| block/qcow2.c | diffblobblamehistory | |
| tests/qemu-iotests/060 | diffblobblamehistory | |
| tests/qemu-iotests/060.out | diffblobblamehistory |