| commit | da24597dd37bc31b4d2328e5542fa3b5676a3fe0 | |
| author | Eric Blake <eblake@redhat.com> | |
| Tue, 7 Sep 2021 17:35:05 +0000 (7 12:35 -0500) | ||
| committer | Eric Blake <eblake@redhat.com> | |
| Wed, 29 Sep 2021 18:46:32 +0000 (29 13:46 -0500) | ||
| tree | bac7bfe0b817f945d0cd2be04a8611a15b4a00e4 | treesnapshot (tar.gz zip) |
| parent | 6a8f3dbb1912141c9806c22db394a9ac8fe8366c | commitdiff |
nbd/server: Allow LIST_META_CONTEXT without STRUCTURED_REPLY
The NBD protocol just relaxed the requirements on
NBD_OPT_LIST_META_CONTEXT:
https://github.com/NetworkBlockDevice/nbd/commit/13a4e33a87
Since listing is not stateful (unlike SET_META_CONTEXT), we don't care
if a client asks for meta contexts without first requesting structured
replies. Well-behaved clients will still ask for structured reply
first (if for no other reason than for back-compat to older servers),
but that's no reason to avoid this change.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20210907173505.1499709-1-eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
The NBD protocol just relaxed the requirements on
NBD_OPT_LIST_META_CONTEXT:
https://github.com/NetworkBlockDevice/nbd/commit/13a4e33a87
Since listing is not stateful (unlike SET_META_CONTEXT), we don't care
if a client asks for meta contexts without first requesting structured
replies. Well-behaved clients will still ask for structured reply
first (if for no other reason than for back-compat to older servers),
but that's no reason to avoid this change.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20210907173505.1499709-1-eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
| nbd/server.c | diffblobblamehistory |