Re: [PATCH 2/3] security: Introduce virSecurityManagerDomainSetIncomingPathLabel

2020-04-17 Thread Erik Skultety
... > > > > > > +/** > > > + * virSecurityManagerDomainSetIncomingPathLabel: > > > + * @mgr: security manager object > > > + * @vm: domain definition object > > > + * @path: path to label > > > + * > > > + * This function relabels given @path so that @vm can restore for > > > > maybe add "host" @p

Re: [PATCH 2/3] security: Introduce virSecurityManagerDomainSetIncomingPathLabel

2020-04-17 Thread Michal Privoznik
On 4/17/20 12:57 PM, Erik Skultety wrote: On Fri, Apr 03, 2020 at 05:58:02PM +0200, Michal Privoznik wrote: This API allows drivers to separate out handling of @stdin_path of virSecurityManagerSetAllLabel(). The thing is, the QEMU driver uses transactions for virSecurityManagerSetAllLabel() whic

Re: [PATCH 2/3] security: Introduce virSecurityManagerDomainSetIncomingPathLabel

2020-04-17 Thread Erik Skultety
On Fri, Apr 03, 2020 at 05:58:02PM +0200, Michal Privoznik wrote: > This API allows drivers to separate out handling of @stdin_path > of virSecurityManagerSetAllLabel(). The thing is, the QEMU driver > uses transactions for virSecurityManagerSetAllLabel() which > relabels devices from inside of dom

[PATCH 2/3] security: Introduce virSecurityManagerDomainSetIncomingPathLabel

2020-04-03 Thread Michal Privoznik
This API allows drivers to separate out handling of @stdin_path of virSecurityManagerSetAllLabel(). The thing is, the QEMU driver uses transactions for virSecurityManagerSetAllLabel() which relabels devices from inside of domain's namespace. This is what we usually want. Except when resuming domain