From: Anisse Astier <1828608@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1828608] [NEW] Chardev websocket might not support pasting more than a few chars
Date: Fri, 10 May 2019 16:24:55 -0000 [thread overview]
Message-ID: <155750549613.15038.5455007066011551794.malonedeb@wampee.canonical.com> (raw)
Public bug reported:
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.
** Affects: qemu
Importance: Undecided
Status: New
** Patch added: "0001-socket-check-char-backend-readiness-before-sending-i.patch"
https://bugs.launchpad.net/bugs/1828608/+attachment/5262964/+files/0001-socket-check-char-backend-readiness-before-sending-i.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1828608
Title:
Chardev websocket might not support pasting more than a few chars
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1828608/+subscriptions
next reply other threads:[~2019-05-10 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 16:24 Anisse Astier [this message]
2019-05-10 16:28 ` [Qemu-devel] [Bug 1828608] Re: Chardev websocket might not support pasting more than a few chars Daniel Berrange
2019-05-13 8:16 ` Anisse Astier
2021-04-22 6:14 ` Thomas Huth
2021-04-30 14:51 ` Anisse Astier
2021-05-04 19:34 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=155750549613.15038.5455007066011551794.malonedeb@wampee.canonical.com \
--to=1828608@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).