Eric Blake 63d5ef869e nbd: Quit server after any write error ... We should never ignore failure from nbd_negotiate_send_rep(); if we are unable to write to the client, then it is not worth trying to continue the negotiation. Fortunately, the problem is not too severe - chances are that the errors being ignored here (mainly inability to write the reply to the client) are indications of a closed connection or something similar, which will also affect the next attempt to interact with the client and eventually reach a point where the errors are detected to end the loop. Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <1463006384-7734-4-git-send-email-eblake@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2016-06-16 18:39:05 +02:00
..
client.c	nbd: More debug typo fixes, use correct formats	2016-06-16 18:39:05 +02:00
common.c	nbd: do not hang nbd_wr_syncv if outside a coroutine and no available data	2016-04-08 00:07:44 +02:00
Makefile.objs	nbd: Split nbd.c	2016-01-15 18:58:02 +01:00
nbd-internal.h	qemu-common: stop including qemu/bswap.h from qemu-common.h	2016-05-19 16:42:28 +02:00
server.c	nbd: Quit server after any write error	2016-06-16 18:39:05 +02:00