Daniel P. Berrangé dd154c4d9f io: fix handling of EOF / error conditions in websock GSource ... We were never reporting the G_IO_HUP event when an end of file was hit on the websocket channel. We also didn't report G_IO_ERR when we hit a fatal error processing the websocket protocol. The latter in particular meant that the chardev code would not notice when an eof/error was encountered on the websocket channel, unless the guest OS happened to trigger a write operation. This meant that once the first client had quit, the chardev would never listen to accept a new client. Fixes launchpad bug 1816819 Acked-by: Stefano Garzarella <sgarzare@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>		2019-03-20 16:56:30 +00:00
..
channel-buffer.c
channel-command.c
channel-file.c
channel-socket.c	io: ensure UNIX client doesn't unlink server socket	2019-01-24 12:23:35 +00:00
channel-tls.c	io: return 0 for EOF in TLS session read after shutdown	2018-11-19 11:16:46 -06:00
channel-util.c	sockets: move fd_is_socket() into common sockets code	2018-03-13 18:06:06 +00:00
channel-watch.c
channel-websock.c	io: fix handling of EOF / error conditions in websock GSource	2019-03-20 16:56:30 +00:00
channel.c	io: Remove redundant read/write_coroutine assignments	2019-02-25 15:03:19 +01:00
dns-resolver.c	qio: non-default context for threaded qtask	2018-03-06 10:19:05 +00:00
Makefile.objs
net-listener.c	Remove unnecessary variables for function return value	2018-05-20 08:48:13 +03:00
task.c	io: add qio_task_wait_thread to join with a background thread	2019-02-12 17:35:56 +01:00
trace-events	io: add qio_task_wait_thread to join with a background thread	2019-02-12 17:35:56 +01:00