diff options
author | Fiona Ebner <f.ebner@proxmox.com> | 2025-05-30 17:11:23 +0200 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2025-07-14 15:42:26 +0200 |
commit | ede0859311e46ca8654eaf11456e19868ac06c66 (patch) | |
tree | 42f42586f322d4054630ff118d70d5b236df0d11 /scripts/tracetool/backend/log.py | |
parent | 6d7e3f8de09d92f9ebea530be3696ed053ae8508 (diff) | |
download | qemu-ede0859311e46ca8654eaf11456e19868ac06c66.zip qemu-ede0859311e46ca8654eaf11456e19868ac06c66.tar.gz qemu-ede0859311e46ca8654eaf11456e19868ac06c66.tar.bz2 |
block: mark bdrv_close() as GRAPH_UNLOCKED
The functions blk_log_writes_close(), blkverify_close(),
quorum_close(), vmdk_close() via vmdk_free_extents(), and other
bdrv_close() implementations call bdrv_graph_wrlock_drained(), which
must be called with the graph unlocked. They are reached via the
BlockDriver's bdrv_close() callback and the bdrv_close() wrapper,
which are also marked as GRAPH_UNLOCKED_PTR and GRAPH_UNLOCKED.
Furthermore, the function bdrv_close() also calls bdrv_drained_begin()
and bdrv_graph_wrlock_drained(), so there are additional reasons for
marking it GRAPH_UNLOCKED.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Message-ID: <20250530151125.955508-47-f.ebner@proxmox.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'scripts/tracetool/backend/log.py')
0 files changed, 0 insertions, 0 deletions