aboutsummaryrefslogtreecommitdiff
path: root/linux-user/sparc64
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2019-01-17 13:36:55 -0600
committerEric Blake <eblake@redhat.com>2019-01-21 15:49:52 -0600
commit0b576b6bfb56291bb13db0a54d99adf2f3706030 (patch)
tree67d570b9e69c1845de12c309fadb7d34a793660b /linux-user/sparc64
parentd21a2d3451d7f1defea5104ce28938f228fab0d4 (diff)
nbd/client: Add meta contexts to nbd_receive_export_list()
We want to be able to detect whether a given qemu NBD server is exposing the right export(s) and dirty bitmaps, at least for regression testing. We could use 'nbd-client -l' from the upstream NBD project to list exports, but it's annoying to rely on out-of-tree binaries; furthermore, nbd-client doesn't necessarily know about all of the qemu NBD extensions. Thus, we plan on adding a new mode to qemu-nbd that merely sniffs all possible information from the server during handshake phase, then disconnects and dumps the information. This patch continues the work of the previous patch, by adding the ability to track the list of available meta contexts into NBDExportInfo. It benefits from the recent refactoring patches with a new nbd_list_meta_contexts() that reuses much of the same framework as setting a meta context. Note: a malicious server could exhaust memory of a client by feeding an unending loop of contexts; perhaps we could place a limit on how many we are willing to receive. But this is no different from our earlier analysis on a server sending an unending list of exports, and the death of a client due to memory exhaustion when the client was going to exit soon anyways is not really a denial of service attack. Signed-off-by: Eric Blake <eblake@redhat.com> Reviewed-by: Richard W.M. Jones <rjones@redhat.com> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Message-Id: <20190117193658.16413-19-eblake@redhat.com>
Diffstat (limited to 'linux-user/sparc64')
0 files changed, 0 insertions, 0 deletions