kernel 2.6.5-1.347 and strange entries in kernel messages after latest selinux update

RaXeT maxer1 at xmission.com
Mon May 3 02:34:32 UTC 2004


I installed kernel 2.6.5-1.347 tonight and mind you I hve selinux=0 on 
kernel boot and I'm now getting selinux activated anyway?

 From messages:

May  2 20:05:35 raxet kernel: SELinux:  Completing initialization.
May  2 20:05:35 raxet kernel: SELinux:  Setting up existing superblocks.
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type 
selinuxfs), uses genfs_contexts
May  2 20:05:35 raxet kernel: SELinux: initialized (dev sda3, type 
ext3), uses xattr
May  2 20:05:35 raxet kernel: SELinux: initialized (dev ram0, type 
ext2), uses xattr
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type mqueue), 
not configured for labeling
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type 
hugetlbfs), not configured for labeling
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type devpts), 
uses transition SIDs
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type 
eventpollfs), uses genfs_contexts
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type pipefs), 
uses task SIDs
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type tmpfs), 
uses transition SIDs
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type futexfs), 
uses genfs_contexts
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type sockfs), 
uses task SIDs
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type proc), 
uses genfs_contexts
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type bdev), 
uses genfs_contexts
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type rootfs), 
uses genfs_contexts
May  2 20:05:35 raxet kernel: SELinux: initialized (dev , type sysfs), 
uses genfs_contexts
May  2 20:05:35 raxet kernel: ieee1394: sbp2: Logged into SBP-2 device
May  2 20:05:35 raxet kernel:   Vendor: LITE-ON   Model: 
LTR-48125W        Rev: VS06
May  2 20:05:35 raxet kernel:   Type:   
CD-ROM                             ANSI SCSI revision: 02
May  2 20:05:35 raxet kernel: audit(1083528291.284:0): avc:  denied  { 
getattr } for  pid=1 exe=/sbin/init path=/dev/initctl dev=sda3 ino=65569 
scontext=system_u:system_r:kernel_t tcontext=system_u:object_r:file_t 
tclass=fifo_file
May  2 20:05:35 raxet kernel: audit(1083528291.284:0): avc:  denied  { 
read write } for  pid=1 exe=/sbin/init name=initctl dev=sda3 ino=65569 
scontext=system_u:system_r:kernel_t tcontext=system_u:object_r:file_t 
tclass=fifo_file
May  2 20:05:35 raxet kernel: audit(1083528292.497:0): avc:  denied  { 
syslog_console } for  pid=672 exe=/bin/dmesg 
scontext=system_u:system_r:kernel_t tcontext=system_u:system_r:kernel_t 
tclass=system
May  2 20:05:35 raxet kernel: audit(1083528292.771:0): avc:  denied  { 
search } for  pid=677 exe=/sbin/sysctl name=net dev= ino=-268435354 
scontext=system_u:system_r:kernel_t 
tcontext=system_u:object_r:sysctl_net_t tclass=dir
May  2 20:05:31 raxet sysctl: kernel.sysrq = 0
May  2 20:05:35 raxet kernel: audit(1083528292.771:0): avc:  denied  { 
write } for  pid=677 exe=/sbin/sysctl name=ip_forward dev= 
ino=-268435331 scontext=system_u:system_r:kernel_t 
tcontext=system_u:object_r:sysctl_net_t tclass=file
May  2 20:05:31 raxet sysctl: kernel.core_uses_pid = 1
May  2 20:05:35 raxet kernel: audit(1083528292.771:0): avc:  denied  { 
getattr } for  pid=677 exe=/sbin/sysctl 
path=/proc/sys/net/ipv4/ip_forward dev= ino=-268435331 
scontext=system_u:system_r:kernel_t 
tcontext=system_u:object_r:sysctl_net_t tclass=file
May  2 20:05:31 raxet network: Setting network parameters:  succeeded

What's with this?

RaXeT





More information about the fedora-test-list mailing list