Eric Blake d8b20291cb nbd/server: Reject 0-length block status request ... The NBD spec says that behavior is unspecified if the client requests 0 length for block status; but since the structured reply is documenting as returning a non-zero length, it's easier to just diagnose this with an EINVAL error than to figure out what to return. CC: qemu-stable@nongnu.org Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <20180621124937.166549-1-eblake@redhat.com> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>		2018-06-21 09:21:34 -05:00
..
client.c	nbd/client: Fix error messages during NBD_INFO_BLOCK_SIZE	2018-05-04 08:23:37 -05: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: Reject 0-length block status request	2018-06-21 09:21:34 -05:00
trace-events	nbd: trace meta context negotiation	2018-04-02 09:10:49 -05:00