summary refs log tree commit diff stats
path: root/results/classifier/108/other/1381
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--results/classifier/108/other/138118
-rw-r--r--results/classifier/108/other/138164248
-rw-r--r--results/classifier/108/other/138184629
-rw-r--r--results/classifier/108/other/138187953
4 files changed, 148 insertions, 0 deletions
diff --git a/results/classifier/108/other/1381 b/results/classifier/108/other/1381
new file mode 100644
index 000000000..98b405d2f
--- /dev/null
+++ b/results/classifier/108/other/1381
@@ -0,0 +1,18 @@
+network: 0.881
+device: 0.876
+graphic: 0.850
+performance: 0.684
+semantic: 0.663
+other: 0.632
+vnc: 0.547
+socket: 0.530
+boot: 0.494
+debug: 0.440
+PID: 0.284
+files: 0.185
+KVM: 0.116
+permissions: 0.048
+
+plugins: plugin_mem_cbs is not consistently NULL'ed when returning from execution
+Description of problem:
+This is an invariant that we should have been checking for; when returning from execution, cpu->plugin_mem_cbs should be NULL. Otherwise we open a door for a use-after-free; admittedly this door isn't that large (it requires a tb_flush to occur while we have the dangling plugin_mem_cbs), but at least one plugin user has encountered this problem: https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg02703.html
diff --git a/results/classifier/108/other/1381642 b/results/classifier/108/other/1381642
new file mode 100644
index 000000000..7a68b9704
--- /dev/null
+++ b/results/classifier/108/other/1381642
@@ -0,0 +1,48 @@
+boot: 0.756
+device: 0.723
+PID: 0.681
+socket: 0.654
+performance: 0.647
+graphic: 0.593
+vnc: 0.584
+network: 0.562
+semantic: 0.496
+permissions: 0.469
+other: 0.390
+files: 0.374
+KVM: 0.274
+debug: 0.240
+
+ecovec.c:66: buffer too small by one.
+
+[qemu-2.1.2/roms/u-boot/board/renesas/ecovec/ecovec.c:66]: (error) Buffer is accessed out of bounds.
+
+    sprintf(env_mac, "%02X:%02X:%02X:%02X:%02X:%02X",
+        mac[0], mac[1], mac[2], mac[3], mac[4], mac[5]);
+
+but
+
+    char env_mac[17];
+
+and 18 into 17 won't go. Suggest increase size of env_mac.
+
+On 15 October 2014 19:00, dcb <email address hidden> wrote:
+> Public bug reported:
+>
+> [qemu-2.1.2/roms/u-boot/board/renesas/ecovec/ecovec.c:66]: (error)
+> Buffer is accessed out of bounds.
+
+This is in the u-boot code which we just carry a copy of
+to produce certain boot ROMs. You should report these
+issues directly to u-boot upstream.
+
+Thanks
+-- PMM
+
+
+FWIW, u-boot was apparently fixed here:
+http://git.denx.de/?p=u-boot.git;a=commitdiff;h=44442c13ba2f63a67664ab5
+
+...and we don't build u-boot for the renesas ecovec, so we don't need to worry about updating our copy of u-boot to something with the fix in it.
+
+
diff --git a/results/classifier/108/other/1381846 b/results/classifier/108/other/1381846
new file mode 100644
index 000000000..c0ce7441e
--- /dev/null
+++ b/results/classifier/108/other/1381846
@@ -0,0 +1,29 @@
+graphic: 0.756
+performance: 0.714
+device: 0.630
+other: 0.596
+network: 0.552
+semantic: 0.535
+permissions: 0.508
+socket: 0.444
+vnc: 0.431
+PID: 0.414
+debug: 0.377
+boot: 0.358
+files: 0.331
+KVM: 0.199
+
+Data sent to parallel port in guest is lost if host buffer fills up
+
+It appears that qemu will blindly write characters out to the chardev and drop them on the floor if a write fails with EAGAIN, without initiating flow control (via BUSY and ACK) back to the guest. If the host buffer is too small, or is talking to a hardware device that is too slow, data will be lost.
+
+I notice this problem when I run a DOS program with this on the qemu command line:
+-parallel /dev/usb/lp0
+
+I can work around this problem by buffering via a pipe, but this looks like a general problem. Is there a way to wire up the readiness of the output chardev to the parallel port ACK and BUSY lines, and signal an ISA interrupt? I don't know the code well enough to tell.
+
+The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
+If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1381879 b/results/classifier/108/other/1381879
new file mode 100644
index 000000000..31cabb789
--- /dev/null
+++ b/results/classifier/108/other/1381879
@@ -0,0 +1,53 @@
+graphic: 0.854
+other: 0.849
+device: 0.793
+socket: 0.723
+KVM: 0.691
+performance: 0.684
+network: 0.674
+PID: 0.640
+debug: 0.638
+files: 0.529
+permissions: 0.521
+semantic: 0.388
+vnc: 0.386
+boot: 0.326
+
+can not run vm with a serial port
+
+environment:
+server: centOS 6.5, 3.14.19, x86_64
+qemu-kvm: QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2), Copyright (c) 2003-2008 Fabrice Bellard
+qemu-system-x86_64 :QEMU emulator version 1.2.0 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard
+virt-manager: 0.9.0
+
+VM: centOS 6.5, 3.12.30, x86_64
+
+reproduce step:
+1. add serial device
+2. select device type: unix socket
+                 device parameters: path=/dev/ttyS0
+                                                       mode=client mode(connect)
+3. run the VM
+
+phenomenon:
+Error starting domain: internal error process exited while connecting to monitor: qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: socket bind failed: Address already in use
+qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: chardev: opening backend "socket" failed
+
+
+Traceback (most recent call last):
+  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper
+    callback(asyncjob, *args, **kwargs)
+  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb
+    callback(*args, **kwargs)
+  File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in startup
+    self._backend.create()
+  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 678, in create
+    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
+libvirtError: internal error process exited while connecting to monitor: qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: socket bind failed: Address already in use
+qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: chardev: opening backend "socket" failed
+
+Opening a socket with the name of a device file can not work, you've got to specify a different name for a unix socket instead. So this is not a bug.
+
+(or if you just wanted to complain about the rather ugly traceback instead of a nice error message: Please file a bug against virt-manager instead. Thanks!)
+