diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2023-09-29 16:51:50 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2023-10-12 16:31:33 +0200 |
| commit | de4fed6f4ef7f2f1a1bce50a2cbbb7fdd397b7ec (patch) | |
| tree | e082983d806ff834220a9d9ad725c91d3e2b044c /qemu-io-cmds.c | |
| parent | 0bb79c97fd8e355aca433f4331d7d45e7e72b4b6 (diff) | |
| download | focaccia-qemu-de4fed6f4ef7f2f1a1bce50a2cbbb7fdd397b7ec.tar.gz focaccia-qemu-de4fed6f4ef7f2f1a1bce50a2cbbb7fdd397b7ec.zip | |
qcow2: Mark qcow2_inactivate() and callers GRAPH_RDLOCK
This adds GRAPH_RDLOCK annotations to declare that callers of qcow2_inactivate() need to hold a reader lock for the graph because it calls bdrv_get_device_or_node_name(), which accesses the parents list of a node. qcow2_do_close() is a bit strange because it is called from different contexts. If close_data_file = true, we know that we were called from non-coroutine main loop context (more specifically, we're coming from qcow2_close()) and can safely drop the reader lock temporarily with bdrv_graph_rdunlock_main_loop() and acquire the writer lock. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20230929145157.45443-16-kwolf@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'qemu-io-cmds.c')
0 files changed, 0 insertions, 0 deletions