Eric Blake ab7c548e26 nbd: Reject unknown request flags ... The NBD protocol says that clients should not send a command flag that has not been negotiated (whether by the client requesting an option during a handshake, or because we advertise support for the flag in response to NBD_OPT_EXPORT_NAME), and that servers should reject invalid flags with EINVAL. We were silently ignoring the flags instead. The client can't rely on our behavior, since it is their fault for passing the bad flag in the first place, but it's better to be robust up front than to possibly behave differently than the client was expecting with the attempted flag. Signed-off-by: Eric Blake <eblake@redhat.com> Reviewed-by: Alex Bligh <alex@alex.org.uk> Message-Id: <1463006384-7734-6-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: Reject unknown request flags	2016-06-16 18:39:05 +02:00