Am 17/08/2023 um 14:50 schrieb Kevin Wolf: > 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> Reviewed-by: Emanuele Giuseppe Esposito <eespo...@redhat.com>
- [PATCH 00/21] Graph locking part 4 (node manage... Kevin Wolf
- [PATCH 20/21] block: Mark bdrv_unref_child... Kevin Wolf
- Re: [PATCH 20/21] block: Mark bdrv_unr... Emanuele Giuseppe Esposito
- Re: [PATCH 20/21] block: Mark bdrv_unr... Stefan Hajnoczi
- [PATCH 03/21] preallocate: Don't poll duri... Kevin Wolf
- Re: [PATCH 03/21] preallocate: Don't p... Eric Blake
- Re: [PATCH 03/21] preallocate: Don't p... Stefan Hajnoczi
- [PATCH 10/21] block: Mark bdrv_attach_chil... Kevin Wolf
- Re: [PATCH 10/21] block: Mark bdrv_att... Stefan Hajnoczi
- [PATCH 14/21] block: Mark bdrv_get_cumulat... Kevin Wolf
- Re: [PATCH 14/21] block: Mark bdrv_get... Emanuele Giuseppe Esposito
- Re: [PATCH 14/21] block: Mark bdrv_get... Stefan Hajnoczi
- [PATCH 15/21] block: Mark bdrv_child_perm(... Kevin Wolf