Re: [libvirt] [PATCH 5/7] util: Introduce and use virObjectRWUnlock

2017-07-31 Thread Michal Privoznik
On 07/28/2017 07:07 PM, Pavel Hrdina wrote: > On Fri, Jul 28, 2017 at 12:38:59PM -0400, John Ferlan wrote: >> Rather than overload virObjectUnlock as commit id '77f4593b' has >> done, create a separate virObjectRWUnlock API that will force the >> consumers to make the proper decision regarding unlo

Re: [libvirt] [PATCH 5/7] util: Introduce and use virObjectRWUnlock

2017-07-28 Thread Pavel Hrdina
On Fri, Jul 28, 2017 at 12:38:59PM -0400, John Ferlan wrote: > Rather than overload virObjectUnlock as commit id '77f4593b' has > done, create a separate virObjectRWUnlock API that will force the > consumers to make the proper decision regarding unlocking the > RWLock's. This restores the virObject

[libvirt] [PATCH 5/7] util: Introduce and use virObjectRWUnlock

2017-07-28 Thread John Ferlan
Rather than overload virObjectUnlock as commit id '77f4593b' has done, create a separate virObjectRWUnlock API that will force the consumers to make the proper decision regarding unlocking the RWLock's. This restores the virObjectUnlock code to using the virObjectGetLockableObj as well. Signed-off