add 18th iteration of classifier

1 files changed, 54 insertions, 0 deletions

diff --git a/results/classifier/118/graphic/1356969 b/results/classifier/118/graphic/1356969
new file mode 100644
index 000000000..27cfffa6b
--- /dev/null
+++ b/results/classifier/118/graphic/1356969
@@ -0,0 +1,54 @@
+graphic: 0.900
+performance: 0.896
+semantic: 0.580
+device: 0.576
+network: 0.528
+ppc: 0.522
+vnc: 0.490
+mistranslation: 0.468
+i386: 0.461
+architecture: 0.446
+socket: 0.438
+risc-v: 0.438
+user-level: 0.423
+boot: 0.417
+VMM: 0.414
+PID: 0.408
+files: 0.381
+TCG: 0.379
+x86: 0.366
+kernel: 0.345
+register: 0.305
+arm: 0.300
+virtual: 0.297
+KVM: 0.291
+peripherals: 0.279
+permissions: 0.278
+hypervisor: 0.264
+debug: 0.247
+assembly: 0.110
+
+qemu-io: the 'map' command hangs 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-io copy.img -c map
+
+Result: qemu-io processes part of the image and then hangs loading 100% of CPU time.
+
+
+qemu.git HEAD 2d591ce2aeebf
+
+
+
+Hi,
+
+well, the issue for this specific image is fixed because it is detected to be corrupt before the mapping can reach the point in question (unaligned L2 table entry). However, commit 4b25bbc4c22cf39350b75bd250d568a4d975f7c5 should have fixed the problem this bug report is really about. Thus, should be fixed.
+
+Thanks for reporting,
+
+Max
+