Re: [PATCH 19/24] block: Introduce bdrv_co_change_backing_file()

2023-11-03 Thread Eric Blake
On Fri, Nov 03, 2023 at 11:33:47AM +0100, Kevin Wolf wrote: > Am 30.10.2023 um 14:57 hat Eric Blake geschrieben: > > On Fri, Oct 27, 2023 at 05:53:28PM +0200, Kevin Wolf wrote: > > > bdrv_change_backing_file() is called both inside and outside coroutine > > > context. This makes it difficult for it

Re: [PATCH 19/24] block: Introduce bdrv_co_change_backing_file()

2023-11-03 Thread Kevin Wolf
Am 30.10.2023 um 14:57 hat Eric Blake geschrieben: > On Fri, Oct 27, 2023 at 05:53:28PM +0200, Kevin Wolf wrote: > > bdrv_change_backing_file() is called both inside and outside coroutine > > context. This makes it difficult for it to take the graph lock > > internally. It also means that driver im

Re: [PATCH 19/24] block: Introduce bdrv_co_change_backing_file()

2023-10-30 Thread Eric Blake
On Fri, Oct 27, 2023 at 05:53:28PM +0200, Kevin Wolf wrote: > bdrv_change_backing_file() is called both inside and outside coroutine > context. This makes it difficult for it to take the graph lock > internally. It also means that driver implementations need to be able to > run outside of coroutine

[PATCH 19/24] block: Introduce bdrv_co_change_backing_file()

2023-10-27 Thread Kevin Wolf
bdrv_change_backing_file() is called both inside and outside coroutine context. This makes it difficult for it to take the graph lock internally. It also means that driver implementations need to be able to run outside of coroutines, too. Switch it to the usual model with a coroutine based implemen