aboutsummaryrefslogtreecommitdiff
path: root/rust/qemu-api-macros
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2025-02-04 22:14:02 +0100
committerKevin Wolf <kwolf@redhat.com>2025-02-06 14:45:58 +0100
commit2849092a0024405e74c96f0a5ec41bb182ec8538 (patch)
tree233d5c9fd669d78a7b584fe44d955858227a9cfa /rust/qemu-api-macros
parent69f28176ca0af850db23a1c6364f0c8525b20801 (diff)
downloadqemu-2849092a0024405e74c96f0a5ec41bb182ec8538.zip
qemu-2849092a0024405e74c96f0a5ec41bb182ec8538.tar.gz
qemu-2849092a0024405e74c96f0a5ec41bb182ec8538.tar.bz2
block: Drain nodes before inactivating them
So far the assumption has always been that if we try to inactivate a node, it is already idle. This doesn't hold true any more if we allow inactivating exported nodes because we can't know when new external requests come in. Drain the node around setting BDRV_O_INACTIVE so that requests can't start operating on an active node and then in the middle it suddenly becomes inactive. With this change, it's enough for exports to check for new requests that they operate on an active node (or, like reads, are allowed even on an inactive node). Signed-off-by: Kevin Wolf <kwolf@redhat.com> Acked-by: Fabiano Rosas <farosas@suse.de> Message-ID: <20250204211407.381505-12-kwolf@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'rust/qemu-api-macros')
0 files changed, 0 insertions, 0 deletions