On 11/30/2010 08:54 PM, Eric Blake wrote:
> * src/security/security_selinux.c
> (SELinuxRestoreSecurityFileLabel): Use selabel_lookup instead of
> matchpathcon.
> Suggested by Daniel Walsh.
> ---
>
> #include
> #include
> +#include
> #include
> #include
> #include
Phooey. This breaks
On 12/13/2010 04:01 PM, Matthias Bolte wrote:
> 2010/12/1 Eric Blake :
>> * src/security/security_selinux.c
>> (SELinuxRestoreSecurityFileLabel): Use selabel_lookup instead of
>> matchpathcon.
>> Suggested by Daniel Walsh.
>> ---
>
> ACK.
Thanks; pushed.
--
Eric Blake ebl...@redhat.com+1-
2010/12/1 Eric Blake :
> * src/security/security_selinux.c
> (SELinuxRestoreSecurityFileLabel): Use selabel_lookup instead of
> matchpathcon.
> Suggested by Daniel Walsh.
> ---
>
> Makes the huge difference that I originally thought I'd get with patch
> 5/n earlier in the series. Beforehand, when
On 11/30/2010 08:54 PM, Eric Blake wrote:
> * src/security/security_selinux.c
> (SELinuxRestoreSecurityFileLabel): Use selabel_lookup instead of
> matchpathcon.
> Suggested by Daniel Walsh.
https://bugzilla.redhat.com/show_bug.cgi?id=658657
> @@ -380,14 +382,16 @@ SELinuxRestoreSecurityFileLabel(
* src/security/security_selinux.c
(SELinuxRestoreSecurityFileLabel): Use selabel_lookup instead of
matchpathcon.
Suggested by Daniel Walsh.
---
Makes the huge difference that I originally thought I'd get with patch
5/n earlier in the series. Beforehand, when trying to start a single
kvm guest the
