1 files changed, 67 insertions, 0 deletions
diff --git a/results/classifier/118/none/1357440 b/results/classifier/118/none/1357440
new file mode 100644
index 00000000..72b24bf6
--- /dev/null
+++ b/results/classifier/118/none/1357440
@@ -0,0 +1,67 @@
+device: 0.595
+PID: 0.565
+files: 0.563
+semantic: 0.495
+network: 0.490
+architecture: 0.459
+graphic: 0.452
+performance: 0.446
+socket: 0.444
+ppc: 0.435
+risc-v: 0.416
+vnc: 0.413
+arm: 0.409
+hypervisor: 0.402
+kernel: 0.400
+permissions: 0.381
+i386: 0.351
+peripherals: 0.337
+x86: 0.328
+boot: 0.323
+VMM: 0.314
+register: 0.309
+TCG: 0.306
+KVM: 0.256
+virtual: 0.249
+assembly: 0.217
+mistranslation: 0.214
+debug: 0.186
+user-level: 0.164
+
+qemu-img: Assert for 'amend' command and the fuzzed image
+
+'qemu-img amend' failed with the assert on the fuzzed image.
+
+Sequence:
+ 1. Unpack the attached archive, make a copy of test.img
+ 2. Put copy.img and backing_img.vdi in the same directory
+ 3. Execute
+   qemu-img amend -o compat=0.10 -f qcow2 copy.img
+
+Result: qemu-img was killed by SIGIOT with the reason:
+
+qemu-img: block/qcow2-cluster.c:1598: expand_zero_clusters_in_l1: Assertion `(cluster_index >= 0) && (cluster_index < *nb_clusters)' failed.
+
+qemu.git HEAD 2d591ce2aeebf
+
+
+
+Hi,
+
+This issue should be fixed by my "[PATCH v3 0/7] block/qcow2: Improve zero cluster expansion" series.
+
+However, there are similar issues in qemu, so we'll probably need a function to quickly mark an image corrupt instead of throwing these assertions.
+
+Max
+
+Hi,
+
+This issue has been fixed in master (af3ff19b48f0bbf3a8bd35c47460358e8c6ae5e5, 2.2.0-rc2):
+
+$ ./qemu-img amend -o compat=0.10 -f qcow2 copy.img
+qemu-img: Error while amending options: File too large
+
+Thanks for your report,
+
+Max
+