Description of problem:

See subject.

Version-Release number of selected component (if applicable):
selinux-policy-3.10.0-56.fc16.noarch
selinux-policy-targeted-3.10.0-56.fc16.noarch


How reproducible:
No idea.

Steps to Reproduce:
No idea.

I was building an f15 package in a local mock-chroot on F16 when SELinux rose this warning.


Actual results:

# sealert -l 478fdd4d-9d85-438c-8603-b05deba84576
SELinux is preventing /sbin/consoletype from read access on the chr_file /dev/null.

*****  Plugin restorecon (98.5 confidence) suggests  *************************

If you want to fix the label. 
/dev/null default label should be null_device_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /dev/null

*****  Plugin leaks (1.48 confidence) suggests  ******************************

If you want to ignore consoletype trying to read access the null chr_file, because you believe it should not need this access.
Then you should report this as a bug.  
You can generate a local policy module to dontaudit this access.
Do
# grep /sbin/consoletype /var/log/audit/audit.log | audit2allow -D -M mypol
# semodule -i mypol.pp

*****  Plugin catchall (1.48 confidence) suggests  ***************************

If you believe that consoletype should be allowed read access on the null chr_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep consoletype /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp


Additional info:
I am occasionally observing f15-mock chroots to do bizarre things (e.g. to kill ypbind). My guess is something in f15 or in mock is massively leaking.