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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



...

> > >
> > > +/**
> > > + * 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" @path here to make it even clearer.
> >
> > > + * it.  This allows the driver backend to use different label than
> > > + * virSecurityManagerDomainSetPathLabel().
>
> This would then be:
>
> This function relabels given @path for read only access, which is in
> contrast with virSecurityManagerDomainSetPathLabel() which gives read write
> access.

Yep, I'm okay with *SetPathLabelRO, don't forget to include ^this commentary
bit :).

--
Erik Skultety





[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux