1 files changed, 43 insertions, 0 deletions
diff --git a/results/classifier/118/none/1572959 b/results/classifier/118/none/1572959
new file mode 100644
index 00000000..8899e8bd
--- /dev/null
+++ b/results/classifier/118/none/1572959
@@ -0,0 +1,43 @@
+device: 0.768
+ppc: 0.742
+socket: 0.683
+vnc: 0.674
+PID: 0.659
+network: 0.658
+register: 0.630
+files: 0.624
+kernel: 0.609
+performance: 0.565
+risc-v: 0.506
+graphic: 0.491
+TCG: 0.480
+VMM: 0.468
+architecture: 0.455
+semantic: 0.452
+boot: 0.426
+x86: 0.424
+mistranslation: 0.391
+arm: 0.386
+i386: 0.382
+KVM: 0.366
+permissions: 0.349
+hypervisor: 0.335
+debug: 0.310
+peripherals: 0.298
+virtual: 0.227
+assembly: 0.216
+user-level: 0.147
+
+bcm2835_property: inconsistent values when both setting and querying the framebuffer 
+
+As the framebuffer settings are copied into the result message before it is reconfigured, inconsistent behavior can happen when, for instance, you set with a single message the width, height, and depth, and ask at the same time to allocate the buffer and get the pitch and the size.
+
+In this case, the reported pitch and size would be incorrect as they were computed with the initial values of width, height and depth, not the ones the client requested.
+
+Attached is a patch also sent to the qemu-devel mailing list.
+
+
+
+The patch had been merged here:
+https://git.qemu.org/?p=qemu.git;a=commitdiff;h=27a5dc7be6a55b60039e3920
+