Re: [libvirt] [PATCH v1 10/11] storage_driver: Protect pool def during startup and build

2019-08-23 Thread John Ferlan
On 5/24/19 10:35 AM, Michal Privoznik wrote: > In near future the storage pool object lock will be released > during startPool and buildPool callback (in some backends). But > this means that another thread may acquire the pool object lock > and change its definition rendering the former thread

Re: [libvirt] [PATCH v1 10/11] storage_driver: Protect pool def during startup and build

2019-08-21 Thread Ján Tomko
On Fri, May 24, 2019 at 04:35:46PM +0200, Michal Privoznik wrote: In near future the storage pool object lock will be released during startPool and buildPool callback (in some backends). But this means that another thread may acquire the pool object lock and change its definition rendering the

[libvirt] [PATCH v1 10/11] storage_driver: Protect pool def during startup and build

2019-05-24 Thread Michal Privoznik
In near future the storage pool object lock will be released during startPool and buildPool callback (in some backends). But this means that another thread may acquire the pool object lock and change its definition rendering the former thread access not only stale definition but also access freed