[Qemu-devel] Chardev bugs that need attention

[Amit Shah <amit.shah@redhat.com>]

Hello,

There are a few bugs for chardev reported by Red Hat and IBM QE
teams.  I haven't been able to get to them in a while, and will note
them down here for whoever wishes to tackle them.

1.  https://bugzilla.redhat.com/show_bug.cgi?id=808295

    There is a reproducer script here:

    https://bugzilla.redhat.com/attachment.cgi?id=573982

    The backtrace with upstream qemu sources is at

    https://bugzilla.redhat.com/show_bug.cgi?id=808295#c40

    and also at

    https://bugzilla.redhat.com/attachment.cgi?id=750770

    This is caused due to a SIGPIPE.


2.  https://bugzilla.redhat.com/show_bug.cgi?id=985205

    Reproduction steps and backtrace mentioned in the bug comment 0.
    This looks like a stale watch remaining behind when a
    virtio-serial port is unplugged, but the chardev exists.


3.  http://wiki.qemu.org/Features/ChardevFlowControl#Known_bugs

    Reproduction steps are mentioned there.  This is about qemu not
    catching -EPIPE for short-lived guest processes and disconnected
    host chardevs.


I will report any progress to the referenced bugzillas and this thread
so that people don't waste time looking at stale stuff.

Thanks,

		Amit