On Fri, 25 Jul 2008, Stephen Smalley wrote: > On Fri, 2008-07-25 at 23:03 +1000, James Morris wrote: > > Turns out it was caused by > > CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX_VALUE being set to the > > default of 19. > > > > After setting it to 22 (same as the Fedora kernel), the problem went away. > > Makes sense - policy.19 predates the avtab memory optimization work I > did, and requires the policy toolchain to fully expand all > attribute-based rules into individual type pairs. So that shows how > much memory we are saving from that particular optimization today. Should we bump that value so that kernel developers don't hit the same problem if they have SELinux enabled? (Many would assume the boot hung). -- James Morris <jmorris@xxxxxxxxx> -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
