Re: [libvirt] [PATCH v4 06/15] security_manager: Rework metadata locking

2018-11-16 Thread Michal Privoznik
On 11/15/18 7:38 PM, John Ferlan wrote: > > > On 11/14/18 7:44 AM, Michal Privoznik wrote: >> Trying to use virlockd to lock metadata turns out to be too big >> gun. Since we will always spawn a separate process for relabeling >> we are safe to use thread unsafe POSIX locks and take out >>

Re: [libvirt] [PATCH v4 06/15] security_manager: Rework metadata locking

2018-11-15 Thread John Ferlan
On 11/14/18 7:44 AM, Michal Privoznik wrote: > Trying to use virlockd to lock metadata turns out to be too big > gun. Since we will always spawn a separate process for relabeling > we are safe to use thread unsafe POSIX locks and take out > virtlockd completely out of the picture. > NB: This

[libvirt] [PATCH v4 06/15] security_manager: Rework metadata locking

2018-11-14 Thread Michal Privoznik
Trying to use virlockd to lock metadata turns out to be too big gun. Since we will always spawn a separate process for relabeling we are safe to use thread unsafe POSIX locks and take out virtlockd completely out of the picture. Signed-off-by: Michal Privoznik --- src/security/security_dac.c