Bug 186741 - serefpolicy 20060323 (2.2.26-1) is locking kernel?
Summary: serefpolicy 20060323 (2.2.26-1) is locking kernel?
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Russell Coker
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-26 00:41 UTC by Robert Scheck
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-04-03 16:44:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2006-03-26 00:41:09 UTC
Description of problem:
Modular policy (serefpolicy) seems to be broken, because when updated to 2.2.26 
once, I can't switch to any other policy (even no downgrade) without rebooting 
the whole system.

Error when trying to downgrade to 2.2.24:
  /usr/sbin/load_policy:  Can't load policy:  Invalid argument
  libsemanage.semanage_reload_policy: load_policy returned error code 2.
  semodule:  Failed!

Undiffing http://cvs.sourceforge.net/viewcvs.py/serefpolicy/refpolicy/policy/
support/loadable_module.spt?r1=1.14&r2=1.15 seems to work around the problem.

Erich from Freenode #selinux already sent a testcase to Stephen, but he didn't 
answer yet. This is maybe a kernel bug, because the policy is correct, but the 
kernel seems to be locked up avoiding to apply a new policy - which only works 
during a reboot (for the moment).

Version-Release number of selected component (if applicable):
selinux-policy-targeted-2.2.26-1

How reproducible:
Everytime, see above.

Actual results:
Broken stuff as described above.

Expected results:
Working like in the past ;-)

Additional info:
There are thousands of avc denieds in my syslog (nearly everything is claimed), 
because of this...and would be very nice to get master of the situation in a 
sane way very soon.

Comment 1 Daniel Walsh 2006-04-03 16:44:36 UTC
Fixed by updates to libsemanage-1.6.2-2


Note You need to log in before you can comment on or make changes to this bug.