Eric Blake f8b3b02933 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> (cherry picked from commit d8b20291cb) Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>		2018-07-18 11:51:25 -05:00
..
Makefile.objs	nbd: Split nbd.c	2016-01-15 18:58:02 +01:00
client.c	nbd/client: fix nbd_negotiate_simple_meta_context	2018-07-11 11:48:21 -05:00
common.c	nbd: BLOCK_STATUS constants	2018-03-01 14:05:24 -06: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-07-18 11:51:25 -05:00
trace-events	nbd: trace meta context negotiation	2018-04-02 09:10:49 -05:00