Re: semodule memory use

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2008-09-10 at 11:50 +1000, Russell Coker wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495786
> 
> I've received the above bug report against the Debian policy packages.  The 
> operation in question is "semodule -b" followed by "semodule -i".
> 
> I haven't had time to work on this (and won't until well after Lenny is 
> released).  But if anyone has any quick ideas of how to reduce memory use by 
> semodule then I would be interested to hear them.

Set expand-check = 0 in /etc/selinux/semanage.conf.
The downside is you'll lose neverallow and hierarchy checking at module
insertion time (but you can get them back at policy build time for the
modules you provide by doing a make validate in refpolicy).  The upside
is that it doesn't have to expand the attributes in rules nor walk them
for neverallow checking or hierarchy checking.

BTW, hierarchy checking really ought to be conditional on whether there
is any hierarchy at all, the way that neverallow checking immediately
returns if there were no neverallow rules.

-- 
Stephen Smalley
National Security Agency


--
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.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux