On 06/21/2018 07:52 AM, Vladimir Sementsov-Ogievskiy wrote:
21.06.2018 15:49, Eric Blake wrote:
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: [email protected]
Signed-off-by: Eric Blake <[email protected]>
Reviewed-by: Vladimir Sementsov-Ogievskiy <[email protected]>
Thanks; added to my NBD queue. Doing this makes it easier to add the
assertion necessary to shut up gcc warning about an uninitialized
variable in the other patches ready to pull.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
