Re: [libvirt] [PATCH v2 02/14] nodedev: Fix locking in virNodeDeviceObjRemove

2017-05-26 Thread John Ferlan
On 05/26/2017 02:57 AM, Peter Krempa wrote: > On Thu, May 25, 2017 at 15:56:59 -0400, John Ferlan wrote: >> The current mechanism doesn't lock each element in devs->objs as it's >> looking at it, rather it keeps locking/unlocking the passed element for >> which the removal is being attempted.

Re: [libvirt] [PATCH v2 02/14] nodedev: Fix locking in virNodeDeviceObjRemove

2017-05-26 Thread Peter Krempa
On Thu, May 25, 2017 at 15:56:59 -0400, John Ferlan wrote: > The current mechanism doesn't lock each element in devs->objs as it's > looking at it, rather it keeps locking/unlocking the passed element for > which the removal is being attempted. Fix things to lock each element > as we're looking

[libvirt] [PATCH v2 02/14] nodedev: Fix locking in virNodeDeviceObjRemove

2017-05-25 Thread John Ferlan
The current mechanism doesn't lock each element in devs->objs as it's looking at it, rather it keeps locking/unlocking the passed element for which the removal is being attempted. Fix things to lock each element as we're looking at them. Signed-off-by: John Ferlan ---