Eric Blake 943cec86d0 nbd: Avoid magic number for NBD max name size ... Declare a constant and use that when determining if an export name fits within the constraints we are willing to support. Note that upstream NBD recently documented that clients MUST support export names of 256 bytes (not including trailing NUL), and SHOULD support names up to 4096 bytes. 4096 is a bit big (we would lose benefits of stack-allocation of a name array), and we already have other limits in place (for example, qcow2 snapshot names are clamped around 1024). So for now, just stick to the required minimum, as that's easier to audit than a full-scale support for larger names. Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <1463006384-7734-12-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: Avoid magic number for NBD max name size	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: Avoid magic number for NBD max name size	2016-06-16 18:39:05 +02:00