Re: [Qemu-devel] [PATCH v2] qemu-char: Do not disconnect when there's data for reading

Zifei Tong writes: > Hi Markus, > > On Thu, Sep 18, 2014 at 8:11 PM, Markus Armbruster wrote: >> Zifei Tong writes: >> >>> After commit 812c1057f6175ac9a9829fa2920a2b5783814193 (Handle G_IO_HUP >>> in tcp_chr_read for tcp chardev), connections are disconnected when in >>> G_IO_HUP condition. >>

Re: [Qemu-devel] [PATCH v2] qemu-char: Do not disconnect when there's data for reading

Hi Markus, On Thu, Sep 18, 2014 at 8:11 PM, Markus Armbruster wrote: > Zifei Tong writes: > >> After commit 812c1057f6175ac9a9829fa2920a2b5783814193 (Handle G_IO_HUP >> in tcp_chr_read for tcp chardev), connections are disconnected when in >> G_IO_HUP condition. >> >> However, it's possible that

Re: [Qemu-devel] [PATCH v2] qemu-char: Do not disconnect when there's data for reading

Zifei Tong writes: > After commit 812c1057f6175ac9a9829fa2920a2b5783814193 (Handle G_IO_HUP > in tcp_chr_read for tcp chardev), connections are disconnected when in > G_IO_HUP condition. > > However, it's possible that there is still data for reading in the channel. > In that case, the remaining

[Qemu-devel] [PATCH v2] qemu-char: Do not disconnect when there's data for reading

After commit 812c1057f6175ac9a9829fa2920a2b5783814193 (Handle G_IO_HUP in tcp_chr_read for tcp chardev), connections are disconnected when in G_IO_HUP condition. However, it's possible that there is still data for reading in the channel. In that case, the remaining data is not handled. I saw a re