Better NBD string length handling
v2 cover Better NBD string length handling
Patch 1 is a revised version after Maxim's comments - it moves the length checks earlier into the system (for cleaner error messages as soon as possible) and adds asserts at the later points that are now guaranteed by the earlier checks. It also covers more string handling, both in the client and in the server, by ensuring that outgoing strings are properly constrained and incoming strings are checked for validity before blind use.
Patch 2 is a new patch, written to make testing of description strings in patch 1 easier.
Eric Blake (2):
nbd: Don't send oversize strings
nbd: Allow description when creating NBD blockdev
qapi/block.json | 8 +++++--- include/block/nbd.h | 1 + block/nbd.c | 9 +++++++++ blockdev-nbd.c | 14 +++++++++++++- monitor/hmp-cmds.c | 4 ++-- nbd/client.c | 16 +++++++++++++--- nbd/server.c | 14 ++++++++++++-- qemu-nbd.c | 9 +++++++++ tests/qemu-iotests/223 | 2 +- tests/qemu-iotests/223.out | 1 + 10 files changed, 66 insertions(+), 12 deletions(-)
Signature · 1 line
2.21.0
PATCH v2 1/2 nbd: Don't send oversize strings
Qemu as server currently won't accept export names larger than 256 bytes, nor create dirty bitmap names longer than 1023 bytes, so most uses of qemu as client or server have no reason to get anywhere near the NBD spec maximum of a 4k limit per string.
However, we weren't actually enforcing things, ignoring when the remote side violates the protocol on input, and also having several code paths where we send oversize strings on output (for example, qemu-nbd --description could easily send more than 4k). Tighten things up as follows:
client:
- Perform bounds check on export name and dirty bitmap request prior to handing it to server
- Validate that copied server replies are not too long (ignoring NBD_INFO_* replies that are not copied is not too bad)
server:
- Perform bounds check on export name and description prior to advertising it to client
- Reject client name or metadata query that is too long
--- include/block/nbd.h | 1 + block/nbd.c | 9 +++++++++ blockdev-nbd.c | 5 +++++ nbd/client.c | 16 +++++++++++++--- nbd/server.c | 14 ++++++++++++-- qemu-nbd.c | 9 +++++++++ 6 files changed, 49 insertions(+), 5 deletions(-)
include/block/nbd.h +1 -0
@@ -232,6 +232,7 @@ enum {* going larger would require an audit of more code to make sure we * aren't overflowing some other buffer. */ #define NBD_MAX_NAME_SIZE 256 +#define NBD_MAX_STRING_SIZE 4096/* Two types of reply structures */ #define NBD_SIMPLE_REPLY_MAGIC 0x67446698
block/nbd.c +9 -0
@@ -1621,6 +1621,10 @@ static int nbd_process_options(BlockDriverState *bs, QDict *options, } s->export =g_strdup (qemu_opt_get (opts,"export" )); +if (s->export &&strlen (s->export) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"export name too long to send to server" ); + goto error; + } s->tlscredsid =g_strdup (qemu_opt_get (opts,"tls-creds" ));if (s->tlscredsid) {
@@ -1638,6 +1642,11 @@ static int nbd_process_options(BlockDriverState *bs, QDict *options, } s->x_dirty_bitmap =g_strdup (qemu_opt_get (opts,"x-dirty-bitmap" )); +if (s->x_dirty_bitmap &&strlen (s->x_dirty_bitmap) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"x_dirty_bitmap query too long to send to server" ); + goto error; + } + s->reconnect_delay =qemu_opt_get_number (opts,"reconnect-delay" ,0 ); ret =0 ;
blockdev-nbd.c +5 -0
@@ -162,6 +162,11 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name, name = device; } +if (strlen (name) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"export name '%s' too long" , name); +return ; + } +if (nbd_export_find (name)) {error_setg (errp,"NBD server already has export named '%s'" , name);return ;
nbd/client.c +13 -3
@@ -289,8 +289,8 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description,return -1 ; } len -=sizeof (namelen); -if (len < namelen) { -error_setg (errp,"incorrect option name length" ); +if (len < namelen || namelen >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"incorrect list name length" );nbd_send_opt_abort (ioc);return -1 ; }
@@ -303,6 +303,11 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, local_name[namelen] ='\0' ; len -= namelen;if (len) { +if (len >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"incorrect list description length" ); +nbd_send_opt_abort (ioc); +return -1 ; + } local_desc =g_malloc (len +1 );if (nbd_read (ioc, local_desc, len,"export description" , errp) <0 ) {nbd_send_opt_abort (ioc);
@@ -479,6 +484,10 @@ static int nbd_opt_info_or_go(QIOChannel *ioc, uint32_t opt,break ;default : +/* +* Not worth the bother to check if NBD_INFO_NAME or +* NBD_INFO_DESCRIPTION exceed NBD_MAX_STRING_SIZE. +*/ trace_nbd_opt_info_unknown (type,nbd_info_lookup (type));if (nbd_drop (ioc, len, errp) <0 ) {error_prepend (errp,"Failed to read info payload: " );
@@ -648,6 +657,7 @@ static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt,if (query) { query_len =strlen (query); data_len +=sizeof (query_len) + query_len; +assert (query_len <=NBD_MAX_STRING_SIZE ); }else {assert (opt ==NBD_OPT_LIST_META_CONTEXT ); }
@@ -1009,7 +1019,7 @@ int nbd_receive_negotiate(AioContext *aio_context, QIOChannel *ioc,bool zeroes;bool base_allocation = info->base_allocation; -assert (info->name); +assert (info->name &&strlen (info->name) <=NBD_MAX_STRING_SIZE );trace_nbd_receive_negotiate_name (info->name); result = nbd_start_negotiate(aio_context, ioc, tlscreds, hostname, outioc,
nbd/server.c +12 -2
@@ -375,6 +375,7 @@ static int nbd_negotiate_send_rep_list(NBDClient *client, NBDExport *exp,trace_nbd_negotiate_send_rep_list (name, desc); name_len =strlen (name); desc_len =strlen (desc); +assert (name_len <=NBD_MAX_STRING_SIZE && desc_len <=NBD_MAX_STRING_SIZE ); len = name_len + desc_len +sizeof (len); ret =nbd_negotiate_send_rep_len (client,NBD_REP_SERVER , len, errp);if (ret <0 ) {
@@ -608,6 +609,7 @@ static int nbd_negotiate_handle_info(NBDClient *client, Error **errp)if (exp->description) {size_t len =strlen (exp->description); +assert (len <=NBD_MAX_STRING_SIZE ); rc =nbd_negotiate_send_info (client,NBD_INFO_DESCRIPTION , len, exp->description, errp);if (rc <0 ) {
@@ -752,6 +754,7 @@ static int nbd_negotiate_send_meta_context(NBDClient *client, {.iov_base = (void *)context, .iov_len = strlen(context)} }; +assert (iov[1 ].iov_len <=NBD_MAX_STRING_SIZE );if (client->opt ==NBD_OPT_LIST_META_CONTEXT ) { context_id =0 ; }
@@ -900,7 +903,7 @@ static int nbd_meta_qemu_query(NBDClient *client, NBDExportMetaContexts *meta,* Parse namespace name and call corresponding function to parse body of the * query. * -* The only supported namespace now is 'base'. +* The only supported namespaces are 'base' and 'qemu'. * * The function aims not wasting time and memory to read long unknown namespace * names.
@@ -926,6 +929,10 @@ static int nbd_negotiate_meta_query(NBDClient *client, } len =cpu_to_be32 (len); +if (len >NBD_MAX_STRING_SIZE ) { +trace_nbd_negotiate_meta_query_skip ("length too long" ); +return nbd_opt_skip (client, len, errp); + }if (len < ns_len) {trace_nbd_negotiate_meta_query_skip ("length too short" );return nbd_opt_skip (client, len, errp);
@@ -1487,7 +1494,7 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset,* access since the export could be available before migration handover. * ctx was acquired in the caller. */ -assert (name); +assert (name &&strlen (name) <=NBD_MAX_STRING_SIZE ); ctx =bdrv_get_aio_context (bs);bdrv_invalidate_cache (bs,NULL );
@@ -1513,6 +1520,7 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset,assert (dev_offset <=INT64_MAX ); exp->dev_offset = dev_offset; exp->name =g_strdup (name); +assert (!desc ||strlen (desc) <=NBD_MAX_STRING_SIZE ); exp->description =g_strdup (desc); exp->nbdflags = (NBD_FLAG_HAS_FLAGS |NBD_FLAG_SEND_FLUSH |NBD_FLAG_SEND_FUA |NBD_FLAG_SEND_CACHE );
@@ -1561,6 +1569,8 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, exp->export_bitmap = bm; exp->export_bitmap_context =g_strdup_printf ("qemu:dirty-bitmap:%s" , bitmap); +/* See BME_MAX_NAME_SIZE in block/qcow2-bitmap.c */ +assert (strlen (exp->export_bitmap_context) <=NBD_MAX_STRING_SIZE ); } exp->close = close;
qemu-nbd.c +9 -0
@@ -826,9 +826,18 @@ int main(int argc, char **argv)break ;case 'x' : export_name = optarg; +if (strlen (export_name) >NBD_MAX_STRING_SIZE ) { +error_report ("export name '%s' too long" , export_name); +exit (EXIT_FAILURE ); + }break ;case 'D' : export_description = optarg; +if (strlen (export_description) >NBD_MAX_STRING_SIZE ) { +error_report ("export description '%s' too long" , + export_description); +exit (EXIT_FAILURE ); + }break ;case 'v' : verbose =1 ;
Signature · 1 line
2.21.0
Re: [PATCH v2 1/2] nbd: Don't send oversize strings
Quoted 36 lines · Eric Blake
Qemu as server currently won't accept export names larger than 256 bytes, nor create dirty bitmap names longer than 1023 bytes, so most uses of qemu as client or server have no reason to get anywhere near the NBD spec maximum of a 4k limit per string.
However, we weren't actually enforcing things, ignoring when the remote side violates the protocol on input, and also having several code paths where we send oversize strings on output (for example, qemu-nbd --description could easily send more than 4k). Tighten things up as follows:
client:
- Perform bounds check on export name and dirty bitmap request prior to handing it to server
- Validate that copied server replies are not too long (ignoring NBD_INFO_* replies that are not copied is not too bad)
server:
- Perform bounds check on export name and description prior to advertising it to client
- Reject client name or metadata query that is too longSigned-off-by Eric Blake <[email protected]>--- include/block/nbd.h | 1 + block/nbd.c | 9 +++++++++ blockdev-nbd.c | 5 +++++ nbd/client.c | 16 +++++++++++++--- nbd/server.c | 14 ++++++++++++-- qemu-nbd.c | 9 +++++++++ 6 files changed, 49 insertions(+), 5 deletions(-)include/block/nbd.h +0
-0
include/block/nbd.h enum { · line 233
Quoted 2 lines
include/block/nbd.h +0
-0@@ -232,6 +232,7 @@ enum {* going larger would require an audit of more code to make sure we * aren't overflowing some other buffer. */
This comment says, that we restrict export name to 256...
Quoted 21 lines
include/block/nbd.h +1
-0#define NBD_MAX_NAME_SIZE 256 +#define NBD_MAX_STRING_SIZE 4096/* Two types of reply structures */ #define NBD_SIMPLE_REPLY_MAGIC 0x67446698block/nbd.c +4
-0@@ -1621,6 +1621,10 @@ static int nbd_process_options(BlockDriverState *bs, QDict *options, } s->export =g_strdup (qemu_opt_get (opts,"export" )); +if (s->export &&strlen (s->export) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"export name too long to send to server" ); + goto error; + } s->tlscredsid =g_strdup (qemu_opt_get (opts,"tls-creds" ));if (s->tlscredsid) {
block/nbd.c static int nbd_process_options(BlockDriverState *bs, QDict *options, · line 1647
Quoted 6 lines
block/nbd.c +3
-0@@ -1638,6 +1642,11 @@ static int nbd_process_options(BlockDriverState *bs, QDict *options, } s->x_dirty_bitmap =g_strdup (qemu_opt_get (opts,"x-dirty-bitmap" )); +if (s->x_dirty_bitmap &&strlen (s->x_dirty_bitmap) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"x_dirty_bitmap query too long to send to server" ); + goto error;
this is new latest "goto error", you should add g_free(s->x_dirty_bitmap) in following "if (ret < 0)"
Quoted 10 lines
block/nbd.c +2
-0+ } + s->reconnect_delay =qemu_opt_get_number (opts,"reconnect-delay" ,0 ); ret =0 ;blockdev-nbd.c +0
-0
blockdev-nbd.c void qmp_nbd_server_add(const char *device, bool has_name, const char *name, · line 168
Quoted 7 lines
blockdev-nbd.c +4
-0@@ -162,6 +162,11 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name, name = device; } +if (strlen (name) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"export name '%s' too long" , name); +return ; + }
Hmmm, no, so here we restrict to 4096, but, we will not allow client to request more than
256. Seems, to correctly update server-part, we should drop NBD_MAX_NAME_SIZE and do the audit mentioned in the comment above its definition.
Quoted 9 lines
blockdev-nbd.c +1
-0+if (nbd_export_find (name)) {error_setg (errp,"NBD server already has export named '%s'" , name);return ;nbd/client.c +0
-0
nbd/client.c static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, · line 293
Quoted 7 lines
nbd/client.c +2
-2@@ -289,8 +289,8 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description,return -1 ; } len -=sizeof (namelen); -if (len < namelen) { -error_setg (errp,"incorrect option name length" ); +if (len < namelen || namelen >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"incorrect list name length" );
New wording made me go above and read the comment, what functions does. Comment is good, but without it, it sounds like name of the list for me...
Quoted 27 lines
nbd/client.c +9
-0nbd_send_opt_abort (ioc);return -1 ; }@@ -303,6 +303,11 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, local_name[namelen] ='\0' ; len -= namelen;if (len) { +if (len >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"incorrect list description length" ); +nbd_send_opt_abort (ioc); +return -1 ; + } local_desc =g_malloc (len +1 );if (nbd_read (ioc, local_desc, len,"export description" , errp) <0 ) {nbd_send_opt_abort (ioc);@@ -479,6 +484,10 @@ static int nbd_opt_info_or_go(QIOChannel *ioc, uint32_t opt,break ;default : +/* +* Not worth the bother to check if NBD_INFO_NAME or +* NBD_INFO_DESCRIPTION exceed NBD_MAX_STRING_SIZE. +*/ trace_nbd_opt_info_unknown (type,nbd_info_lookup (type));if (nbd_drop (ioc, len, errp) <0 ) {error_prepend (errp,"Failed to read info payload: " );
nbd/client.c static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt, · line 663
Quoted 7 lines
nbd/client.c +1
-0@@ -648,6 +657,7 @@ static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt,if (query) { query_len =strlen (query); data_len +=sizeof (query_len) + query_len; +assert (query_len <=NBD_MAX_STRING_SIZE ); }else {assert (opt ==NBD_OPT_LIST_META_CONTEXT ); }
you may assert export_len as well..
Quoted 75 lines
nbd/client.c +1
-1@@ -1009,7 +1019,7 @@ int nbd_receive_negotiate(AioContext *aio_context, QIOChannel *ioc,bool zeroes;bool base_allocation = info->base_allocation; -assert (info->name); +assert (info->name &&strlen (info->name) <=NBD_MAX_STRING_SIZE );trace_nbd_receive_negotiate_name (info->name); result = nbd_start_negotiate(aio_context, ioc, tlscreds, hostname, outioc,nbd/server.c +10
-2@@ -375,6 +375,7 @@ static int nbd_negotiate_send_rep_list(NBDClient *client, NBDExport *exp,trace_nbd_negotiate_send_rep_list (name, desc); name_len =strlen (name); desc_len =strlen (desc); +assert (name_len <=NBD_MAX_STRING_SIZE && desc_len <=NBD_MAX_STRING_SIZE ); len = name_len + desc_len +sizeof (len); ret =nbd_negotiate_send_rep_len (client,NBD_REP_SERVER , len, errp);if (ret <0 ) {@@ -608,6 +609,7 @@ static int nbd_negotiate_handle_info(NBDClient *client, Error **errp)if (exp->description) {size_t len =strlen (exp->description); +assert (len <=NBD_MAX_STRING_SIZE ); rc =nbd_negotiate_send_info (client,NBD_INFO_DESCRIPTION , len, exp->description, errp);if (rc <0 ) {@@ -752,6 +754,7 @@ static int nbd_negotiate_send_meta_context(NBDClient *client, {.iov_base = (void *)context, .iov_len = strlen(context)} }; +assert (iov[1 ].iov_len <=NBD_MAX_STRING_SIZE );if (client->opt ==NBD_OPT_LIST_META_CONTEXT ) { context_id =0 ; }@@ -900,7 +903,7 @@ static int nbd_meta_qemu_query(NBDClient *client, NBDExportMetaContexts *meta,* Parse namespace name and call corresponding function to parse body of the * query. * -* The only supported namespace now is 'base'. +* The only supported namespaces are 'base' and 'qemu'. * * The function aims not wasting time and memory to read long unknown namespace * names. @@ -926,6 +929,10 @@ static int nbd_negotiate_meta_query(NBDClient *client, } len =cpu_to_be32 (len); +if (len >NBD_MAX_STRING_SIZE ) { +trace_nbd_negotiate_meta_query_skip ("length too long" ); +return nbd_opt_skip (client, len, errp); + }if (len < ns_len) {trace_nbd_negotiate_meta_query_skip ("length too short" );return nbd_opt_skip (client, len, errp);@@ -1487,7 +1494,7 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset,* access since the export could be available before migration handover. * ctx was acquired in the caller. */ -assert (name); +assert (name &&strlen (name) <=NBD_MAX_STRING_SIZE ); ctx =bdrv_get_aio_context (bs);bdrv_invalidate_cache (bs,NULL );@@ -1513,6 +1520,7 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset,assert (dev_offset <=INT64_MAX ); exp->dev_offset = dev_offset; exp->name =g_strdup (name); +assert (!desc ||strlen (desc) <=NBD_MAX_STRING_SIZE ); exp->description =g_strdup (desc); exp->nbdflags = (NBD_FLAG_HAS_FLAGS |NBD_FLAG_SEND_FLUSH |NBD_FLAG_SEND_FUA |NBD_FLAG_SEND_CACHE );
nbd/server.c NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, · line 1572
Quoted 4 lines
nbd/server.c +1
-0@@ -1561,6 +1569,8 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, exp->export_bitmap = bm; exp->export_bitmap_context =g_strdup_printf ("qemu:dirty-bitmap:%s" , bitmap); +/* See BME_MAX_NAME_SIZE in block/qcow2-bitmap.c */
Hmm. BME_MAX_NAME_SIZE is checked only when creating persistent bitmaps. But for non-persistent name length is actually unlimited. So, we should either limit all bitmap names to 1023 (hope, this will not break existing scenarios) or error out here (or earlier) instead of assertion.
We also may want QEMU_BUILD_BUG_ON(NBD_MAX_STRING_SIZE < BME_MAX_NAME_SIZE + sizeof("qemu:dirty-bitmap:") - 1)
Quoted 28 lines
nbd/server.c +1
-0+assert (strlen (exp->export_bitmap_context) <=NBD_MAX_STRING_SIZE ); } exp->close = close;qemu-nbd.c +9
-0@@ -826,9 +826,18 @@ int main(int argc, char **argv)break ;case 'x' : export_name = optarg; +if (strlen (export_name) >NBD_MAX_STRING_SIZE ) { +error_report ("export name '%s' too long" , export_name); +exit (EXIT_FAILURE ); + }break ;case 'D' : export_description = optarg; +if (strlen (export_description) >NBD_MAX_STRING_SIZE ) { +error_report ("export description '%s' too long" , + export_description); +exit (EXIT_FAILURE ); + }break ;case 'v' : verbose =1 ;
Signature · 2 lines
Best regards, Vladimir
Re: [PATCH v2 1/2] nbd: Don't send oversize strings
Quoted 25 lines · Vladimir Sementsov-Ogievskiy
Quoted 23 lines · Eric Blake
Qemu as server currently won't accept export names larger than 256 bytes, nor create dirty bitmap names longer than 1023 bytes, so most uses of qemu as client or server have no reason to get anywhere near the NBD spec maximum of a 4k limit per string.
However, we weren't actually enforcing things, ignoring when the remote side violates the protocol on input, and also having several code paths where we send oversize strings on output (for example, qemu-nbd --description could easily send more than 4k). Tighten things up as follows:
client:
- Perform bounds check on export name and dirty bitmap request prior to handing it to server
- Validate that copied server replies are not too long (ignoring NBD_INFO_* replies that are not copied is not too bad)
server:
- Perform bounds check on export name and description prior to advertising it to client
- Reject client name or metadata query that is too longSigned-off-by Eric Blake <[email protected]>---
Quoted 6 lines
include/block/nbd.h enum { · line 233
Quoted 4 lines
+++
b/include/block/nbd.hinclude/block/nbd.h +0
-0@@ -232,6 +232,7 @@ enum {* going larger would require an audit of more code to make sure we * aren't overflowing some other buffer. */ This comment says, that we restrict export name to 256...
Yes, because we still stack-allocate the name in places, but 4k is too large for stack allocation. But we're inconsistent on where we use the smaller 256-limit; the server won't serve an image that large, but doesn't prevent a client from requesting a 4k name export (even though that export will not be present).
Quoted 5 lines
Quoted 5 lines
blockdev-nbd.c +1
-0+++ b/blockdev-nbd.c@@ -162,6 +162,11 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name, name = device; }
Quoted 8 lines
blockdev-nbd.c void qmp_nbd_server_add(const char *device, bool has_name, const char *name, · line 168
Quoted 4 lines
blockdev-nbd.c +4
-0+if (strlen (name) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"export name '%s' too long" , name); +return ; + }Hmmm, no, so here we restrict to 4096, but, we will not allow client to request more than
256. Seems, to correctly update server-part, we should dropNBD_MAX_NAME_SIZEand do the audit mentioned in the comment above its definition.
Yeah, I guess it's time to just get rid of NBD_MAX_NAME_SIZE, and move away from stack allocations. Should I do that as a followup to this patch, or spin a v3?
Quoted 4 lines
Quoted 4 lines
(quoted diff) +1
-0+++ b/nbd/client.c@@ -289,8 +289,8 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, return -1; }
Quoted 8 lines
nbd/client.c static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, · line 293
Quoted 5 lines
nbd/client.c +2
-2len -=sizeof (namelen); -if (len < namelen) { -error_setg (errp,"incorrect option name length" ); +if (len < namelen || namelen >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"incorrect list name length" );New wording made me go above and read the comment, what functions does. Comment is good, but without it, it sounds like name of the list for me...
Maybe:
incorrect name length in server's list response
Quoted 10 lines
nbd/client.c static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, · line 307
Quoted 10 lines
nbd/client.c +2
-0nbd_send_opt_abort (ioc);return -1 ; }@@ -303,6 +303,11 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, local_name[namelen] ='\0' ; len -= namelen;if (len) { +if (len >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"incorrect list description length" );
and
incorrect description length in server's list response
Quoted 10 lines
nbd/client.c static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt, · line 663
Quoted 8 lines
nbd/client.c +1
-0@@ -648,6 +657,7 @@ static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt,if (query) { query_len =strlen (query); data_len +=sizeof (query_len) + query_len; +assert (query_len <=NBD_MAX_STRING_SIZE ); }else {assert (opt ==NBD_OPT_LIST_META_CONTEXT ); }you may assert
export_lenas well..
It was asserted earlier, but doing it again might not hurt, especially if I do the followup patch getting rid of NBD_MAX_NAME_SIZE
Quoted 9 lines
nbd/server.c NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, · line 1572
Quoted 5 lines
nbd/server.c +1
-0@@ -1561,6 +1569,8 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, exp->export_bitmap = bm; exp->export_bitmap_context =g_strdup_printf ("qemu:dirty-bitmap:%s" , bitmap); +/* See BME_MAX_NAME_SIZE in block/qcow2-bitmap.c */ Hmm.
BME_MAX_NAME_SIZEis checked only when creating persistent bitmaps. But for non-persistent name length is actually unlimited. So, we should either limit all bitmap names to 1023 (hope, this will not break existing scenarios) or error out here (or earlier) instead of assertion.
I'm leaning towards limiting ALL bitmaps to the same length (as we've already debated the idea of being able to convert an existing bitmap from transient to persistent).
Quoted 2 lines
We also may want
QEMU_BUILD_BUG_ON(NBD_MAX_STRING_SIZE < BME_MAX_NAME_SIZE + sizeof("qemu:dirty-bitmap:") - 1)
Except that BME_MAX_NAME_SIZE is not (currently) in a public .h file.
Signature · 3 lines
Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
Vladimir Sementsov-Ogievskiy
Reviewed-byRe: [PATCH v2 1/2] nbd: Don't send oversize strings
Quoted 50 lines · Eric Blake
Quoted 25 lines · Vladimir Sementsov-Ogievskiy
Quoted 23 lines · Eric Blake
Qemu as server currently won't accept export names larger than 256 bytes, nor create dirty bitmap names longer than 1023 bytes, so most uses of qemu as client or server have no reason to get anywhere near the NBD spec maximum of a 4k limit per string.
However, we weren't actually enforcing things, ignoring when the remote side violates the protocol on input, and also having several code paths where we send oversize strings on output (for example, qemu-nbd --description could easily send more than 4k). Tighten things up as follows:
client:
- Perform bounds check on export name and dirty bitmap request prior to handing it to server
- Validate that copied server replies are not too long (ignoring NBD_INFO_* replies that are not copied is not too bad) server:
- Perform bounds check on export name and description prior to advertising it to client
- Reject client name or metadata query that is too longSigned-off-by Eric Blake <[email protected]>---
Quoted 6 lines
include/block/nbd.h enum { · line 233
Quoted 4 lines
+++
b/include/block/nbd.hinclude/block/nbd.h +0
-0@@ -232,6 +232,7 @@ enum {* going larger would require an audit of more code to make sure we * aren't overflowing some other buffer. */ This comment says, that we restrict export name to 256...
Yes, because we still stack-allocate the name in places, but 4k is too large for stack allocation. But we're inconsistent on where we use the smaller 256-limit; the server won't serve an image that large, but doesn't prevent a client from requesting a 4k name export (even though that export will not be present).
Quoted 5 lines
Quoted 5 lines
blockdev-nbd.c +1
-0+++ b/blockdev-nbd.c@@ -162,6 +162,11 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name, name = device; }Quoted 8 lines
blockdev-nbd.c void qmp_nbd_server_add(const char *device, bool has_name, const char *name, · line 168
Quoted 4 lines
blockdev-nbd.c +4
-0+ if (strlen(name) > NBD_MAX_STRING_SIZE) { + error_setg(errp, "export name '%s' too long", name); + return; + }Hmmm, no, so here we restrict to 4096, but, we will not allow client to request more than
256. Seems, to correctly update server-part, we should dropNBD_MAX_NAME_SIZEand do the audit mentioned in the comment above its definition.
Quoted 1 line
Yeah, I guess it's time to just get rid of
NBD_MAX_NAME_SIZE, and move away from stack allocations. Should I do that as a followup to this patch, or spin a v3?
Hmm. It's OK too.
With
- fixed mem-leak in nbd_process_options
- s/x_dirty_bitmap/x-dirty-bitmap in nbd_process_options in error message
- following yours new wordings
However, this patch introduces possible crash point, asserting on bitmap name below, so it would better be fixed before this patch or immediately after it.. Still, it's unlikely to have a bitmap with name longer than 4k..
Quoted 14 lines
Quoted 13 lines
nbd/client.c static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, · line 293
Quoted 10 lines
nbd/client.c +3
-2+++ b/nbd/client.c@@ -289,8 +289,8 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, return -1; } len -= sizeof(namelen); - if (len < namelen) { - error_setg(errp, "incorrect option name length"); + if (len < namelen || namelen > NBD_MAX_STRING_SIZE) { + error_setg(errp, "incorrect list name length");New wording made me go above and read the comment, what functions does. Comment is good, but without it, it sounds like name of the list for me...
Quoted 3 lines
Maybe:
incorrect name length in server's list response
Yes, this is better, thanks
Quoted 41 lines
Quoted 11 lines
nbd/client.c static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, · line 307
Quoted 11 lines
nbd/client.c +2
-0nbd_send_opt_abort(ioc); return -1; }@@ -303,6 +303,11 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, local_name[namelen] = '\0'; len -= namelen; if (len) { + if (len > NBD_MAX_STRING_SIZE) { + error_setg(errp, "incorrect list description length");and
incorrect description length in server's list response
Quoted 10 lines
nbd/client.c static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt, · line 663
Quoted 8 lines
nbd/client.c +1
-0@@ -648,6 +657,7 @@ static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt, if (query) { query_len = strlen(query); data_len += sizeof(query_len) + query_len; + assert(query_len <= NBD_MAX_STRING_SIZE); } else { assert(opt == NBD_OPT_LIST_META_CONTEXT); }you may assert
export_lenas well..It was asserted earlier, but doing it again might not hurt, especially if I do the followup patch getting rid of
NBD_MAX_NAME_SIZEQuoted 9 lines
nbd/server.c NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, · line 1572
Quoted 5 lines
nbd/server.c +1
-0@@ -1561,6 +1569,8 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, exp->export_bitmap = bm; exp->export_bitmap_context = g_strdup_printf("qemu:dirty-bitmap:%s", bitmap); + /* See BME_MAX_NAME_SIZE in block/qcow2-bitmap.c */Hmm.
BME_MAX_NAME_SIZEis checked only when creating persistent bitmaps. But for non-persistent name length is actually unlimited. So, we should either limit all bitmap names to 1023 (hope, this will not break existing scenarios) or error out here (or earlier) instead of assertion.
Quoted 1 line
I'm leaning towards limiting ALL bitmaps to the same length (as we've already debated the idea of being able to convert an existing bitmap from transient to persistent).
Agreed, but ..
Quoted 6 lines
Quoted 3 lines
We also may want
QEMU_BUILD_BUG_ON(NBD_MAX_STRING_SIZE < BME_MAX_NAME_SIZE + sizeof("qemu:dirty-bitmap:") - 1)Except that
BME_MAX_NAME_SIZEis not (currently) in a public .h file.
.. I think, than it should be new BLOCK_DIRTY_BITMAP_MAX_NAME_SIZE.. And we'll have to note it in qapi doc.. Should this change go through deprecation? Or we consider non-persistent bitmaps as something not really useful?
Signature · 2 lines
Best regards, Vladimir
Re: [PATCH v2 1/2] nbd: Don't send oversize strings
Quoted 133 lines · Vladimir Sementsov-Ogievskiy
Quoted 50 lines · Eric Blake
Quoted 22 lines · Vladimir Sementsov-Ogievskiy
Quoted 21 lines · Eric Blake
Qemu as server currently won't accept export names larger than 256 bytes, nor create dirty bitmap names longer than 1023 bytes, so most uses of qemu as client or server have no reason to get anywhere near the NBD spec maximum of a 4k limit per string.
However, we weren't actually enforcing things, ignoring when the remote side violates the protocol on input, and also having several code paths where we send oversize strings on output (for example, qemu-nbd --description could easily send more than 4k). Tighten things up as follows:
client:
- Perform bounds check on export name and dirty bitmap request prior to handing it to server
- Validate that copied server replies are not too long (ignoring NBD_INFO_* replies that are not copied is not too bad)
server:
- Perform bounds check on export name and description prior to advertising it to client
- Reject client name or metadata query that is too longQuoted 8 lines
include/block/nbd.h enum { · line 233
Quoted 6 lines
Signed-off-by Eric Blake <[email protected]>---
+++b/include/block/nbd.hinclude/block/nbd.h +0
-0@@ -232,6 +232,7 @@ enum {* going larger would require an audit of more code to make sure we * aren't overflowing some other buffer. */ This comment says, that we restrict export name to 256...
Yes, because we still stack-allocate the name in places, but 4k is too large for stack allocation. But we're inconsistent on where we use the smaller 256-limit; the server won't serve an image that large, but doesn't prevent a client from requesting a 4k name export (even though that export will not be present).
Quoted 5 lines
Quoted 5 lines
blockdev-nbd.c +1
-0+++ b/blockdev-nbd.c@@ -162,6 +162,11 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name, name = device; }Quoted 8 lines
blockdev-nbd.c void qmp_nbd_server_add(const char *device, bool has_name, const char *name, · line 168
Quoted 4 lines
blockdev-nbd.c +4
-0+if (strlen (name) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"export name '%s' too long" , name); +return ; + }Hmmm, no, so here we restrict to 4096, but, we will not allow client to request more than
256. Seems, to correctly update server-part, we should dropNBD_MAX_NAME_SIZEand do the audit mentioned in the comment above its definition.Quoted 1 line
Yeah, I guess it's time to just get rid of
NBD_MAX_NAME_SIZE, and move away from stack allocations. Should I do that as a followup to this patch, or spin a v3?Hmm. It's OK too.
With
- fixed mem-leak innbd_process_options
- s/x_dirty_bitmap/x-dirty-bitmap innbd_process_optionsin error message
- following yours new wordingsReviewed-by Vladimir Sementsov-Ogievskiy <[email protected]>However, this patch introduces possible crash point, asserting on bitmap name below, so it would better be fixed before this patch or immediately after it.. Still, it's unlikely to have a bitmap with name longer than 4k..
Quoted 14 lines
Quoted 13 lines
nbd/client.c static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, · line 293
Quoted 10 lines
nbd/client.c +3
-2+++ b/nbd/client.c@@ -289,8 +289,8 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description,return -1 ; } len -=sizeof (namelen); -if (len < namelen) { -error_setg (errp,"incorrect option name length" ); +if (len < namelen || namelen >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"incorrect list name length" );New wording made me go above and read the comment, what functions does. Comment is good, but without it, it sounds like name of the list for me...
Quoted 3 lines
Maybe:
incorrect name length in server's list response
Yes, this is better, thanks
Quoted 41 lines
Quoted 11 lines
nbd/client.c static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, · line 307
Quoted 11 lines
nbd/client.c +2
-0nbd_send_opt_abort (ioc);return -1 ; }@@ -303,6 +303,11 @@ static int nbd_receive_list(QIOChannel *ioc, char **name, char **description, local_name[namelen] ='\0' ; len -= namelen;if (len) { +if (len >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"incorrect list description length" );and
incorrect description length in server's list response
Quoted 10 lines
nbd/client.c static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt, · line 663
Quoted 8 lines
nbd/client.c +1
-0@@ -648,6 +657,7 @@ static int nbd_send_meta_query(QIOChannel *ioc, uint32_t opt,if (query) { query_len =strlen (query); data_len +=sizeof (query_len) + query_len; +assert (query_len <=NBD_MAX_STRING_SIZE ); }else {assert (opt ==NBD_OPT_LIST_META_CONTEXT ); }you may assert
export_lenas well..It was asserted earlier, but doing it again might not hurt, especially if I do the followup patch getting rid of
NBD_MAX_NAME_SIZEQuoted 9 lines
nbd/server.c NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, · line 1572
Quoted 5 lines
nbd/server.c +1
-0@@ -1561,6 +1569,8 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, exp->export_bitmap = bm; exp->export_bitmap_context =g_strdup_printf ("qemu:dirty-bitmap:%s" , bitmap); +/* See BME_MAX_NAME_SIZE in block/qcow2-bitmap.c */ Hmm.
BME_MAX_NAME_SIZEis checked only when creating persistent bitmaps. But for non-persistent name length is actually unlimited. So, we should either limit all bitmap names to 1023 (hope, this will not break existing scenarios) or error out here (or earlier) instead of assertion.Quoted 1 line
I'm leaning towards limiting ALL bitmaps to the same length (as we've already debated the idea of being able to convert an existing bitmap from transient to persistent).
Agreed, but ..
Quoted 2 lines
Quoted 2 lines
Quoted 11 lines
Quoted 4 lines
Quoted 1 line
We also may want
QEMU_BUILD_BUG_ON(NBD_MAX_STRING_SIZE < BME_MAX_NAME_SIZE + sizeof("qemu:dirty-bitmap:") - 1)Except that
BME_MAX_NAME_SIZEis not (currently) in a public .h file... I think, than it should be new
BLOCK_DIRTY_BITMAP_MAX_NAME_SIZE.. And we'll have to note it in qapi doc.. Should this change go through deprecation? Or we consider non-persistent bitmaps as something not really useful?Signature · 2 lines
Best regards, Vladimir
I followed upon the new patch and the comments, and it seems ok now to me, (including the comments that were already made) but I haven't checked if there are more cases of missing length checks.
Best regards,
Maxim Levitsky
Re: [PATCH v2 1/2] nbd: Don't send oversize strings
In reply to Vladimir Sementsov-OgievskiyQuoted 9 lines · Vladimir Sementsov-Ogievskiy
Quoted 9 lines
Quoted 9 lines
nbd/server.c NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, · line 1572
Quoted 5 lines
nbd/server.c +1
-0@@ -1561,6 +1569,8 @@ NBDExport *nbd_export_new(BlockDriverState *bs, uint64_t dev_offset, exp->export_bitmap = bm; exp->export_bitmap_context = g_strdup_printf("qemu:dirty-bitmap:%s", bitmap); + /* See BME_MAX_NAME_SIZE in block/qcow2-bitmap.c */Hmm.
BME_MAX_NAME_SIZEis checked only when creating persistent bitmaps. But for non-persistent name length is actually unlimited. So, we should either limit all bitmap names to 1023 (hope, this will not break existing scenarios) or error out here (or earlier) instead of assertion.
I'm seriously doubting that any existing scenarios try to use a name that long. If no one was relying on a long name (especially since it was inconsistent between persistent being limited to qcow2 constraints and non-persistent having no limit), we can consider it as a bug-fix rather than something needing a deprecation period.
Quoted 7 lines
Quoted 2 lines
I'm leaning towards limiting ALL bitmaps to the same length (as we've already debated the idea of being able to convert an existing bitmap from transient to persistent).
Agreed, but ..
Quoted 2 lines
Quoted 2 lines
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
We also may want
QEMU_BUILD_BUG_ON(NBD_MAX_STRING_SIZE < BME_MAX_NAME_SIZE + sizeof("qemu:dirty-bitmap:") - 1)Except that
BME_MAX_NAME_SIZEis not (currently) in a public .h file... I think, than it should be new
BLOCK_DIRTY_BITMAP_MAX_NAME_SIZE.. And we'll have to note it in qapi doc.. Should this change go through deprecation? Or we consider non-persistent bitmaps as something not really useful?
I'm preparing a v3 patch that just goes ahead and adds the limit on bitmap names everywhere, as a separate patch.
Signature · 3 lines
Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
PATCH v2 2/2 nbd: Allow description when creating NBD blockdev
In reply to Eric BlakeAllow blockdevs to match the feature already present in qemu-nbd -D. Enhance iotest 223 to cover it.
--- qapi/block.json | 8 +++++--- blockdev-nbd.c | 9 ++++++++- monitor/hmp-cmds.c | 4 ++-- tests/qemu-iotests/223 | 2 +- tests/qemu-iotests/223.out | 1 + 5 files changed, 17 insertions(+), 7 deletions(-)
qapi/block.json +5 -3
@@ -250,9 +250,11 @@ # @name: Export name. If unspecified, the @device parameter is used as the # export name. (Since 2.12) # +# @description: Free-form description of the export. (Since 4.2) +# # @writable: Whether clients should be able to write to the device via the # NBD connection (default false). - +# # @bitmap: Also export the dirty bitmap reachable from @device, so the # NBD client can use NBD_OPT_SET_META_CONTEXT with # "qemu:dirty-bitmap:NAME" to inspect the bitmap. (since 4.0)
@@ -263,8 +265,8 @@ # Since: 1.3.0 ## { 'command': 'nbd-server-add', - 'data': {'device': 'str', '*name': 'str', '*writable': 'bool', - '*bitmap': 'str' } } + 'data': {'device': 'str', '*name': 'str', '*description': 'str', + '*writable': 'bool', '*bitmap': 'str' } } ## # @NbdServerRemoveMode:
blockdev-nbd.c +8 -1
@@ -144,6 +144,7 @@ void qmp_nbd_server_start(SocketAddressLegacy *addr, }void qmp_nbd_server_add (const char *device,bool has_name,const char *name, +bool has_description,const char *description,bool has_writable,bool writable,bool has_bitmap,const char *bitmap,Error **errp) {
@@ -167,6 +168,11 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name,return ; } +if (has_description &&strlen (description) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"description '%s' too long" , description); +return ; + } +if (nbd_export_find (name)) {error_setg (errp,"NBD server already has export named '%s'" , name);return ;
@@ -195,7 +201,8 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name, writable = false; } - exp =nbd_export_new (bs,0 , len, name,NULL , bitmap, !writable, !writable, + exp =nbd_export_new (bs,0 , len, name, description, bitmap, + !writable, !writable,NULL , false, on_eject_blk, errp);if (!exp) { goto out;
monitor/hmp-cmds.c +2 -2
@@ -2352,7 +2352,7 @@ void hmp_nbd_server_start(Monitor *mon, const QDict *qdict)continue ; } -qmp_nbd_server_add (info->value->device, false,NULL , +qmp_nbd_server_add (info->value->device, false,NULL , false,NULL , true, writable, false,NULL , &local_err);if (local_err !=NULL ) {
@@ -2374,7 +2374,7 @@ void hmp_nbd_server_add(Monitor *mon, const QDict *qdict)bool writable =qdict_get_try_bool (qdict,"writable" , false);Error *local_err =NULL ; -qmp_nbd_server_add (device, !!name, name, true, writable, +qmp_nbd_server_add (device, !!name, name, false,NULL , true, writable, false,NULL , &local_err);hmp_handle_error (mon, &local_err); }
tests/qemu-iotests/223 +1 -1
@@ -144,7 +144,7 @@ _send_qemu_cmd $QEMU_HANDLE '{"execute":"nbd-server-add", "bitmap":"b3"}}' "error" # Missing bitmap _send_qemu_cmd $QEMU_HANDLE '{"execute":"nbd-server-add", "arguments":{"device":"n", "name":"n2", "writable":true, - "bitmap":"b2"}}' "return" + "description":"some text", "bitmap":"b2"}}' "return" $QEMU_NBD_PROG -L -k "$TEST_DIR/nbd" echo
tests/qemu-iotests/223.out +1 -0
@@ -49,6 +49,7 @@ exports available: 2 base:allocation qemu:dirty-bitmap:b export: 'n2' + description: some text size: 4194304 flags: 0xced ( flush fua trim zeroes df cache fast-zero ) min block: 1
Signature · 1 line
2.21.0
Re: [PATCH v2 2/2] nbd: Allow description when creating NBD blockdev
Quoted 4 lines · Eric Blake
Allow blockdevs to match the feature already present in qemu-nbd -D. Enhance iotest 223 to cover it.
Signed-off-by Eric Blake <[email protected]>
Quoted 13 lines
--- qapi/block.json | 8 +++++--- blockdev-nbd.c | 9 ++++++++- monitor/hmp-cmds.c | 4 ++-- tests/qemu-iotests/223 | 2 +- tests/qemu-iotests/223.out | 1 + 5 files changed, 17 insertions(+), 7 deletions(-)qapi/block.json +0
-0
qapi/block.json line 253
Quoted 4 lines
qapi/block.json +1
-0@@ -250,9 +250,11 @@ # @name: Export name. If unspecified, the @device parameter is used as the # export name. (Since 2.12) # +# @description: Free-form description of the export. (Since 4.2)
Worth mention maximum of 4096?
Quoted 11 lines
qapi/block.json +2
-1+# # @writable: Whether clients should be able to write to the device via the # NBD connection (default false). - +# # @bitmap: Also export the dirty bitmap reachable from @device, so the # NBD client can use NBD_OPT_SET_META_CONTEXT with # "qemu:dirty-bitmap:NAME" to inspect the bitmap. (since 4.0)@@ -263,8 +265,8 @@ # Since: 1.3.0 ##
[..]
Signature · 2 lines
Best regards, Vladimir
Re: [PATCH v2 2/2] nbd: Allow description when creating NBD blockdev
In reply to Eric BlakeQuoted 114 lines · Eric Blake
Allow blockdevs to match the feature already present in qemu-nbd -D. Enhance iotest 223 to cover it.
Signed-off-by Eric Blake <[email protected]>--- qapi/block.json | 8 +++++--- blockdev-nbd.c | 9 ++++++++- monitor/hmp-cmds.c | 4 ++-- tests/qemu-iotests/223 | 2 +- tests/qemu-iotests/223.out | 1 + 5 files changed, 17 insertions(+), 7 deletions(-)qapi/block.json +5
-3@@ -250,9 +250,11 @@ # @name: Export name. If unspecified, the @device parameter is used as the # export name. (Since 2.12) # +# @description: Free-form description of the export. (Since 4.2) +# # @writable: Whether clients should be able to write to the device via the # NBD connection (default false). - +# # @bitmap: Also export the dirty bitmap reachable from @device, so the # NBD client can use NBD_OPT_SET_META_CONTEXT with # "qemu:dirty-bitmap:NAME" to inspect the bitmap. (since 4.0)@@ -263,8 +265,8 @@ # Since: 1.3.0 ## { 'command': 'nbd-server-add', - 'data': {'device': 'str', '*name': 'str', '*writable': 'bool', - '*bitmap': 'str' } } + 'data': {'device': 'str', '*name': 'str', '*description': 'str', + '*writable': 'bool', '*bitmap': 'str' } } ## # @NbdServerRemoveMode:blockdev-nbd.c +8
-1@@ -144,6 +144,7 @@ void qmp_nbd_server_start(SocketAddressLegacy *addr, }void qmp_nbd_server_add (const char *device,bool has_name,const char *name, +bool has_description,const char *description,bool has_writable,bool writable,bool has_bitmap,const char *bitmap,Error **errp) {@@ -167,6 +168,11 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name,return ; } +if (has_description &&strlen (description) >NBD_MAX_STRING_SIZE ) { +error_setg (errp,"description '%s' too long" , description); +return ; + } +if (nbd_export_find (name)) {error_setg (errp,"NBD server already has export named '%s'" , name);return ;@@ -195,7 +201,8 @@ void qmp_nbd_server_add(const char *device, bool has_name, const char *name, writable = false; } - exp =nbd_export_new (bs,0 , len, name,NULL , bitmap, !writable, !writable, + exp =nbd_export_new (bs,0 , len, name, description, bitmap, + !writable, !writable,NULL , false, on_eject_blk, errp);if (!exp) { goto out;monitor/hmp-cmds.c +2
-2@@ -2352,7 +2352,7 @@ void hmp_nbd_server_start(Monitor *mon, const QDict *qdict)continue ; } -qmp_nbd_server_add (info->value->device, false,NULL , +qmp_nbd_server_add (info->value->device, false,NULL , false,NULL , true, writable, false,NULL , &local_err);if (local_err !=NULL ) {@@ -2374,7 +2374,7 @@ void hmp_nbd_server_add(Monitor *mon, const QDict *qdict)bool writable =qdict_get_try_bool (qdict,"writable" , false);Error *local_err =NULL ; -qmp_nbd_server_add (device, !!name, name, true, writable, +qmp_nbd_server_add (device, !!name, name, false,NULL , true, writable, false,NULL , &local_err);hmp_handle_error (mon, &local_err); }tests/qemu-iotests/223 +1
-1@@ -144,7 +144,7 @@ _send_qemu_cmd $QEMU_HANDLE '{"execute":"nbd-server-add", "bitmap":"b3"}}' "error" # Missing bitmap _send_qemu_cmd $QEMU_HANDLE '{"execute":"nbd-server-add", "arguments":{"device":"n", "name":"n2", "writable":true, - "bitmap":"b2"}}' "return" + "description":"some text", "bitmap":"b2"}}' "return" $QEMU_NBD_PROG -L -k "$TEST_DIR/nbd" echotests/qemu-iotests/223.out +0
-0
tests/qemu-iotests/223.out exports available: 2 · line 55
Quoted 7 lines
tests/qemu-iotests/223.out +1
-0@@ -49,6 +49,7 @@ exports available: 2 base:allocation qemu:dirty-bitmap:b export: 'n2' + description: some text size: 4194304 flags: 0xced ( flush fua trim zeroes df cache fast-zero ) min block: 1
Best regards,
Maxim Levitsky