nbd/client: Request extended headers during negotiation
commit56cf9d0471c6481adcada2b6afbaf6c7af9e76c7
authorEric Blake <eblake@redhat.com>
Mon, 25 Sep 2023 19:22:39 +0000 (25 14:22 -0500)
committerEric Blake <eblake@redhat.com>
Thu, 5 Oct 2023 16:02:08 +0000 (5 11:02 -0500)
tree0f36010f63c81ed5a8423436ff3a5f31c0c96647
parenta7c18670b429cc5e9c5e6a25cc401dc93086f1a7
nbd/client: Request extended headers during negotiation

All the pieces are in place for a client to finally request extended
headers.  Note that we must not request extended headers when qemu-nbd
is used to connect to the kernel module (as nbd.ko does not expect
them, but expects us to do the negotiation in userspace before handing
the socket over to the kernel), but there is no harm in all other
clients requesting them.

Extended headers are not essential to the information collected during
'qemu-nbd --list', but probing for it gives us one more piece of
information in that output.  Update the iotests affected by the new
line of output.

Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-ID: <20230925192229.3186470-23-eblake@redhat.com>
nbd/client-connection.c
nbd/client.c
qemu-nbd.c
tests/qemu-iotests/223.out
tests/qemu-iotests/233.out
tests/qemu-iotests/241.out
tests/qemu-iotests/307.out
tests/qemu-iotests/tests/nbd-qemu-allocation.out