diff options
| author | Eric Blake <eblake@redhat.com> | 2018-11-29 20:32:31 -0600 |
|---|---|---|
| committer | Eric Blake <eblake@redhat.com> | 2018-11-30 14:11:20 -0600 |
| commit | 47829c40794160debdb33b4a042d182e776876d4 (patch) | |
| tree | f930cfaed80247e2c3424b5722aed0767bef5a0a /tests/vhost-user-bridge.c | |
| parent | e31d802479df9daff1994a7ed1e36bbc5bb19d03 (diff) | |
| download | qemu-47829c40794160debdb33b4a042d182e776876d4.zip qemu-47829c40794160debdb33b4a042d182e776876d4.tar.gz qemu-47829c40794160debdb33b4a042d182e776876d4.tar.bz2 | |
nbd/client: Make x-dirty-bitmap more reliable
The implementation of x-dirty-bitmap in qemu 3.0 (commit 216ee365)
silently falls back to treating the server as not supporting
NBD_CMD_BLOCK_STATUS if a requested meta_context name was not
negotiated, which in turn means treating the _entire_ image as
data. Since our hack relied on using 'qemu-img map' to view
which portions of the image were dirty by seeing what the
redirected bdrv_block_status() treats as holes, this means
that our fallback treats the entire image as clean. Better
would have been to treat the entire image as dirty, or to fail
to connect because the user's request for a specific context
could not be honored. This patch goes with the latter.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20181130023232.3079982-3-eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Diffstat (limited to 'tests/vhost-user-bridge.c')
0 files changed, 0 insertions, 0 deletions