Vladimir Sementsov-Ogievskiy 37e02aebf8 nbd/server: fix sparse read ... In case of io error in nbd_co_send_sparse_read we should not "goto reply:", as it was a fatal error and the common behavior is to disconnect in this case. We should not try to send the client an additional error reply, since we already hit a channel-io error on our previous attempt to send one. Fix this by handling block-status error in nbd_co_send_sparse_read, so nbd_co_send_sparse_read fails only on io error. Then just skip common "reply:" code path in nbd_trip. Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Message-Id: <20180308184636.178534-3-vsementsov@virtuozzo.com> [eblake: grammar tweaks] Signed-off-by: Eric Blake <eblake@redhat.com>		2018-03-13 15:38:55 -05:00
..
client.c	qio: non-default context for TLS handshake	2018-03-06 10:19:07 +00:00
common.c	nbd: BLOCK_STATUS constants	2018-03-01 14:05:24 -06:00
Makefile.objs	nbd: Split nbd.c	2016-01-15 18:58:02 +01:00
nbd-internal.h	nbd: Minimal structured read for client	2017-10-30 21:48:41 +01:00
server.c	nbd/server: fix sparse read	2018-03-13 15:38:55 -05:00
trace-events	nbd/client: fix error messages in nbd_handle_reply_err	2018-03-01 14:48:23 -06:00