Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: update fails, saying: Output from selinux-policy-targeted-3.6.32-116.fc12@noarch: SELinux: Could not load policy file /etc/selinux/targeted/policy/policy.24: Invalid argument /sbin/load_policy: Can't load policy: Invalid argument libsemanage.semanage_reload_policy: load_policy returned error code 2. semodule: Failed! Version-Release number of selected component (if applicable): 3.6.32-116.fc12 How reproducible: happens when i updated the package Steps to Reproduce: 1.update 2. 3. Actual results: above Expected results: working Additional info:
Could you try again. yum reinstall selinux-policy-targeted I believe this is a kernel issue.
Daniel, should he attach is /var/log/dmesg || dmesg.old logfile?
daniel - i tried the yum reinstall and it appears to have worked. thus: Installing : selinux-policy-targeted-3.6.32-116.fc12.noarch 1/1 Installed: selinux-policy-targeted.noarch 0:3.6.32-116.fc12 Complete!
Created attachment 423370 [details] dmesg per request
load_policy: page allocation failure. order:4, mode:0xc0d0 Pid: 9491, comm: load_policy Tainted: P 2.6.32.12-115.fc12.x86_64 #1 Call Trace: [<ffffffff810dcb9c>] __alloc_pages_nodemask+0x5ad/0x631 [<ffffffff811051af>] alloc_pages_current+0x95/0x9e [<ffffffff810db436>] __get_free_pages+0xe/0x4b [<ffffffff8110e2a8>] __kmalloc+0x47/0x15e [<ffffffff811f7716>] avtab_alloc+0x59/0x9e [<ffffffff811f784e>] avtab_read+0x73/0xed [<ffffffff811f9929>] policydb_read+0x4d6/0x1301 [<ffffffff810468ed>] ? __dequeue_entity+0x33/0x38 [<ffffffff811fcf5a>] security_load_policy+0x119/0x38c [<ffffffff810f0537>] ? handle_mm_fault+0x35a/0x7bd [<ffffffff810fae06>] ? vmap_page_range_noflush+0x1fe/0x2db [<ffffffff8101268e>] ? common_interrupt+0xe/0x13 [<ffffffff814591ef>] ? do_page_fault+0x270/0x2a0 [<ffffffff814570e5>] ? page_fault+0x25/0x30 [<ffffffff811f31cd>] ? sel_write_load+0x7a/0x61a [<ffffffff811f31fe>] sel_write_load+0xab/0x61a [<ffffffff8122f116>] ? might_fault+0x21/0x23 [<ffffffff811ef6e6>] ? selinux_file_permission+0x5c/0xb3 [<ffffffff811e5a61>] ? security_file_permission+0x16/0x18 [<ffffffff8111bb64>] vfs_write+0xae/0x10b [<ffffffff8111bc81>] sys_write+0x4a/0x6e [<ffffffff81011d32>] system_call_fastpath+0x16/0x1b
fixed in commit 6c9ff1013b7a21099da838eeef7c3f23ee347957 in 2.6.34 kernels and later. Since the worst that happens is that you don't get the new policy until the next reboot I don't think there is much else we will do here. Thanks for the report!