performance: 0.525
semantic: 0.504
graphic: 0.446
device: 0.389
user-level: 0.380
files: 0.357
PID: 0.344
ppc: 0.316
kernel: 0.300
architecture: 0.282
x86: 0.268
network: 0.267
hypervisor: 0.258
VMM: 0.256
vnc: 0.248
KVM: 0.247
socket: 0.234
virtual: 0.219
permissions: 0.218
mistranslation: 0.215
i386: 0.206
risc-v: 0.203
TCG: 0.192
arm: 0.191
debug: 0.189
register: 0.185
boot: 0.184
assembly: 0.156
peripherals: 0.141

qemu-img: Killed by SIGTRAP on check of the fuzzed image

'qemu-img check -r all' was killed by SIGTRAP.

Sequence:
 1. Unpack the attached archive, make a copy of test.img
 2. Put copy.img and backing_img.qed in the same directory
 3. Execute

qemu-img check -f qcow2 -r all copy.img

Result: qemu-img was killed by SIGTRAP with the reason:

(process:2210): GLib-ERROR **: gmem.c:140: failed to allocate 18446744069633940288 bytes

The qemu-img execution log can be found in the attached archive.

qemu.git HEAD 2d591ce2aeebf



Hi,

This issue has at least been partially fixed in master (5f77ef69a195098baddfdc6d189f1b4a94587378):

$ ./qemu-img check -f qcow2 -r all copy.img
# ...
The following inconsistencies were found and repaired:

    0 leaked clusters
    1 corruptions

Double checking the fixed image now...

469 errors were found on the image.
Data may be corrupted, or further writes to the image may corrupt it.

4766 internal errors have occurred during the check.
2459/4434 = 55.46% allocated, 99.31% fragmented, 10.41% compressed clusters
Image end offset: 2048

As with bug 1355697, I'm still working on the repair function. But this image is broken in a way that there's no real way to fix it. The best we could do is ask the user to use qemu-img convert and then hope for the best. I'll just mark this as fixed.

Max