Re: [PATCH] move genhomedircon call out of transaction

[Ivan Gyurdiev <ivg2@cornell.edu>]

>> Attached is a patch that moves the genhomedircon patch out of the 
>> libsemanage transaction.  This is necessary since genhomedircon now 
>> uses libsemanage, and enters a transaction itself.
>>   
> I don't think genhomedircon enters a transaction... nor should it - 
> it's a read-only operation with respect to the objects that we manage 
> (currently). I could be wrong, but I can't find where it enters a 
> transaction in the patch.
Note: calling multiple semanage query functions outside a transaction is 
a bad idea, because a policy is object is created and destroyed per call 
(while it is cached when in-transaction). However, here only the list() 
function is called (once?), so that seems fine. The active lock guards 
against modification during list().


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.