I've had 3 oopses in the last week that I've been playing with selinux.
ksymoops decoded results are attached. The first occurred when I was
trying to reload the policy:
Nov 21 19:33:24 bench3 kernel: ss: loading policy configuration from /ss_policy Nov 21 19:33:24 bench3 kernel: security: 4 users, 5 roles, 349 types Nov 21 19:33:24 bench3 kernel: security: 29 classes, 60594 rules Nov 21 19:33:24 bench3 kernel: Unable to handle kernel paging request at virtual address 465ec21c
The system was still useable but attempts to reload the policy were hanging so I rebooted.
The other two happened when nobody was doing anything with the system except cron running the normal stuff.
Nov 22 14:40:00 tracy kernel: task_precondition: assigning context system_u:system_r:crond_t to pid 1620 exe=/usr/sbin/crond Nov 22 14:40:00 tracy kernel: Unable to handle kernel paging request at virtual address 00732528
Nov 22 14:41:00 tracy kernel: <1>Unable to handle kernel paging request at virtual address a8d4b5ec
After this the system was hung solid, no ping or anything.
-- Tracy Reed http://www.ultraviolet.orgFrom: Stephen Smalley <sds_at_tislabs.com>
-- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.
On Mon, 26 Nov 2001, Tracy R Reed wrote:
> I've had 3 oopses in the last week that I've been playing with selinux.
Looks like you're still using the 2.4.12-based SELinux rather than the latest release, and it doesn't look like you've applied patches that have been posted since that release. Make sure that you've at least applied these patches:
http://marc.theaimsgroup.com/?l=selinux&m=100378165408266&w=2 http://marc.theaimsgroup.com/?l=selinux&m=100445617604999&w=2
The first kernel Oops definitely looked like the load_policy bug fixed by the second patch above. I'm not sure about the latter two Oopses - I haven't seen them, and they weren't in SELinux code. Could be a side effect of one of the two bugs for which we've posted patches.
If you upgrade to the latest release, be sure to apply the selinux_inode_delete patch.
-- Stephen D. Smalley, NAI Labs ssmalley@nai.com -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.
This archive was generated by hypermail 2.2.0 on Wed 11 Jun 2008 - 08:10:54 EDT