1 files changed, 69 insertions, 0 deletions
diff --git a/results/classifier/118/x86/1819108 b/results/classifier/118/x86/1819108
new file mode 100644
index 000000000..3e9009048
--- /dev/null
+++ b/results/classifier/118/x86/1819108
@@ -0,0 +1,69 @@
+x86: 0.934
+vnc: 0.761
+device: 0.684
+kernel: 0.624
+KVM: 0.601
+PID: 0.547
+architecture: 0.535
+performance: 0.490
+mistranslation: 0.484
+semantic: 0.415
+network: 0.413
+socket: 0.391
+peripherals: 0.379
+user-level: 0.308
+boot: 0.293
+virtual: 0.292
+ppc: 0.288
+graphic: 0.284
+register: 0.265
+hypervisor: 0.255
+files: 0.219
+permissions: 0.211
+debug: 0.198
+VMM: 0.170
+risc-v: 0.131
+TCG: 0.120
+i386: 0.110
+arm: 0.078
+assembly: 0.073
+
+qemu-bridge-helper failure but qemu not exit
+
+When qemu-bridge-helper run failed, its parent process qemu is still alive.
+This is my command line:
+
+qemu-system-x86_64 -curses -enable-kvm -cpu host -smp 4 -m 4096 \
+  -vnc :1 \
+  -kernel /data/xugang_vms/boot/vmlinuz \
+  -initrd /data/xugang_vms/boot/initram \
+  -append 'module_blacklist=drm,evbug net.ifnames=0 biosdevname=0 ROOTDEV=rootfs' \
+  -drive file=/data/xugang_vms/instances/vn7/rootfs.img,format=qcow2,if=virtio \
+  -monitor unix:/data/xugang_vms/var/monitor/vn7.sock,server,nowait \
+  -netdev bridge,br=vmbr99,helper="/root/bridgehelper --ns=kvm_1 ",id=n1 -device virtio-net,netdev=n1,mac=92:99:98:76:01:07
+
+"/root/bridgehelper" is self defined helper binary by me. But after bridge-helper exited with failure(not send fd to qemu process yet), the linux vm's console will be messed up. I checked the qemu source code(at net/tap.c) and found following snip:
+
+===>
+do {
+            fd = recv_fd(sv[0]);
+        } while (fd == -1 && errno == EINTR);
+        saved_errno = errno;
+
+        close(sv[0]);
+
+        while (waitpid(pid, &status, 0) != pid) {
+            /* loop */
+        }
+<=========
+
+why recv_fd will infinitely wait for recv? Maybe it shall waitpid and then recv_fd ?
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/166
+
+