On Thu, Aug 17, 2023 at 02:50:19PM +0200, Kevin Wolf wrote: > Instead of taking the writer lock internally, require callers to already > hold it when calling bdrv_unref_child(). These callers will typically > already hold the graph lock once the locking work is completed, which > means that they can't call functions that take it internally. > > Signed-off-by: Kevin Wolf <kw...@redhat.com> > --- > include/block/block-global-state.h | 7 ++++++- > block.c | 11 +++++++---- > block/blklogwrites.c | 4 ++++ > block/blkverify.c | 2 ++ > block/qcow2.c | 4 +++- > block/quorum.c | 6 ++++++ > block/replication.c | 3 +++ > block/snapshot.c | 2 ++ > block/vmdk.c | 11 +++++++++++ > tests/unit/test-bdrv-drain.c | 8 ++++++-- > 10 files changed, 50 insertions(+), 8 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefa...@redhat.com>
signature.asc
Description: PGP signature
