1 files changed, 73 insertions, 0 deletions
diff --git a/results/classifier/118/none/1828608 b/results/classifier/118/none/1828608
new file mode 100644
index 000000000..5ef16e60a
--- /dev/null
+++ b/results/classifier/118/none/1828608
@@ -0,0 +1,73 @@
+socket: 0.574
+semantic: 0.536
+device: 0.531
+user-level: 0.505
+performance: 0.409
+mistranslation: 0.389
+network: 0.377
+permissions: 0.342
+ppc: 0.323
+vnc: 0.289
+PID: 0.289
+hypervisor: 0.288
+kernel: 0.281
+architecture: 0.271
+register: 0.228
+graphic: 0.228
+risc-v: 0.222
+files: 0.210
+virtual: 0.206
+peripherals: 0.198
+boot: 0.196
+VMM: 0.184
+TCG: 0.162
+x86: 0.158
+arm: 0.157
+debug: 0.155
+KVM: 0.153
+i386: 0.129
+assembly: 0.078
+
+Chardev websocket might not support pasting more than a few chars
+
+When sending more than 4-5 characters on the websocket serial console (with pasting for example), the guest might not receive all of them, or worse interpret the input as Magic SysRq keys.
+
+This might be due to the io loop not checking the backend readiness before calling the read function.
+
+Attached patched fixes the problem on my system. I'm not sure it's the proper approach, this is just to start discussion.
+
+
+
+If the problem only happens with a websockets channel enabled, it possibly a bug in the QIOChannelWebsock impl rather than the chardev
+
+I wrote a websocket client to help reproduce the bug without a browser:
+https://github.com/anisse/websocktty
+
+You can install it to your $GOPATH/bin (defaults to ~/go/bin) with "go get github.com/anisse/websocktty"
+
+I can reproduce the bug with it by simply pasting a long-enough (5 to 20 characters) string.
+
+I could not reproduce the bug with qemu's  "-serial tcp" and netcat, so this problem might indeed be limited to the websock channel implementation.
+
+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 please 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.
+
+The bug is still present.
+
+
+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/133
+
+