qemu/qapi
Eric Blake cf7c49cf6a bitmap: Enforce maximum bitmap name length
We document that for qcow2 persistent bitmaps, the name cannot exceed
1023 bytes.  It is inconsistent if transient bitmaps do not have to
abide by the same limit, and it is unlikely that any existing client
even cares about using bitmap names this long.  It's time to codify
that ALL bitmaps managed by qemu (whether persistent in qcow2 or not)
have a documented maximum length.

Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20191114024635.11363-3-eblake@redhat.com>
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
2019-11-18 16:01:34 -06:00
..
audio.json audio: add mixing-engine option (documentation) 2019-10-18 08:14:05 +02:00
authz.json
block-core.json bitmap: Enforce maximum bitmap name length 2019-11-18 16:01:34 -06:00
block.json
char.json
common.json
crypto.json
dump.json
error.json
introspect.json qapi: Add feature flags to commands 2019-10-22 13:54:13 +02:00
job.json
machine-target.json target/arm/monitor: Introduce qmp_query_cpu_model_expansion 2019-11-01 08:49:10 +00:00
machine.json
Makefile.objs
migration.json migration: add new migration state wait-unplug 2019-10-29 18:55:26 -04:00
misc-target.json
misc.json qapi: Allow introspecting fix for savevm's cooperation with blockdev 2019-10-22 13:54:14 +02:00
net.json qapi: add failover negotiated event 2019-10-29 18:55:26 -04:00
opts-visitor.c
qapi-clone-visitor.c
qapi-dealloc-visitor.c
qapi-schema.json
qapi-util.c
qapi-visit-core.c
qdev.json
qmp-dispatch.c
qmp-event.c
qmp-registry.c
qobject-input-visitor.c
qobject-output-visitor.c
qom.json
rdma.json
rocker.json
run-state.json
sockets.json
string-input-visitor.c
string-output-visitor.c
tpm.json
trace-events
trace.json
transaction.json
ui.json