Why did SELinux relable my filesystem?

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/25/2013 06:25 AM, Steven P. Ulrick wrote:
> Hello, Everyone During my most recent re-boot, SELinux relabled my entire
> filesystem. Which would be fine, except for the fact that I have SELinux
> disabled on my system:
> 
>> # This file controls the state of SELinux on the system. # SELINUX= can
>> take one of these three values: #     enforcing - SELinux security policy
>> is enforced. #     permissive - SELinux prints warnings instead of
>> enforcing. #     disabled - No SELinux policy is loaded. 
>> SELINUX=disabled # SELINUXTYPE= can take one of these two values: #
>> targeted - Targeted processes are protected, #     minimum - Modification
>> of targeted policy. Only selected processes are protected. #     mls -
>> Multi Level Security protection. SELINUXTYPE=targeted
> 
> Why did SELinux, which is disabled on my system, spend all that time
> re-labeling my filesystem?
> 
> Steven P. Ulrick
> 
There was a bug in libselinux update that caused this problem, it should now
be fixed in libselinux-2.2.1-6.fc20

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLFiE8ACgkQrlYvE4MpobPA4QCfV6DSX1UEgeFOYJpXmFw7uTnN
AMYAn2HhQxpKtKapSGXm5RjZW0lnNqNF
=JBIW
-----END PGP SIGNATURE-----