Re: [PULL 11/23] Revert "graph-lock: Disable locking for now"

On Jul 10 14:40, Kevin Wolf wrote: > Am 10.07.2023 um 14:22 hat Klaus Jensen geschrieben: > > On Jun 28 16:15, Kevin Wolf wrote: > > > Now that bdrv_graph_wrlock() temporarily drops the AioContext lock that > > > its caller holds, it can poll without causing deadlocks. We can now > > > re-enable

Re: [PULL 11/23] Revert "graph-lock: Disable locking for now"

Am 10.07.2023 um 14:22 hat Klaus Jensen geschrieben: > On Jun 28 16:15, Kevin Wolf wrote: > > Now that bdrv_graph_wrlock() temporarily drops the AioContext lock that > > its caller holds, it can poll without causing deadlocks. We can now > > re-enable graph locking. > > > > This reverts commit

Re: [PULL 11/23] Revert "graph-lock: Disable locking for now"

On Jun 28 16:15, Kevin Wolf wrote: > Now that bdrv_graph_wrlock() temporarily drops the AioContext lock that > its caller holds, it can poll without causing deadlocks. We can now > re-enable graph locking. > > This reverts commit ad128dff0bf4b6f971d05eb4335a627883a19c1d. > I'm seeing a pretty

[PULL 11/23] Revert "graph-lock: Disable locking for now"

Now that bdrv_graph_wrlock() temporarily drops the AioContext lock that its caller holds, it can poll without causing deadlocks. We can now re-enable graph locking. This reverts commit ad128dff0bf4b6f971d05eb4335a627883a19c1d. Signed-off-by: Kevin Wolf Message-ID: