From: Paul Moore <paul.moore@hp.com>
To: Matt Anderson <mra@hp.com>
Cc: James Morris <jmorris@namei.org>, selinux@tycho.nsa.gov
Subject: Re: SELinux policy and performance impacts
Date: Fri, 8 Aug 2008 10:15:19 -0400 [thread overview]
Message-ID: <200808081015.19599.paul.moore@hp.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0808080955290.22387@tundra.namei.org>
On Thursday 07 August 2008 8:03:02 pm James Morris wrote:
> On Thu, 7 Aug 2008, Matt Anderson wrote:
> > I'm currently looking into the performance impact of SELinux. Most
> > of what I have seen so far involve testing the system's performance
> > with file creation, open, and exec, but I was hoping to gather some
> > more data before finalizing any conclusions.
> >
> > I was wondering if anyone knows of any types of policy rules that
> > when loaded into the kernel are particularly detrimental to system
> > performance. My understanding is that all policy rules are treated
> > equally once they've been compiled to binary, but I wanted to ask
> > here first in order to confirm that.
>
> Yes, all access rules are applied in a standard form with decisions
> cached in the AVC. There were some network permissions which had to
> do a full policydb lookup on each packet to determine the label to
> use, but these are also now cached (although will still incur some
> overhead).
As an FYI, you'll want 2.6.26 to get the all of the cached network
permissions; 2.6.25 added interface and node caches, 2.6.26 added port
caches. If you are looking at network performance as part of this you
will want to make sure compat_net is disabled, i.e. use Secmark.
Ideally you would also enable the new network_peer_controls policy
capability but I don't think we have that enabled by default just yet,
needs more testing I believe.
--
paul moore
linux @ hp
--
This message was distributed to subscribers of the selinux mailing 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.
next prev parent reply other threads:[~2008-08-08 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 23:13 SELinux policy and performance impacts Matt Anderson
2008-08-08 0:03 ` James Morris
2008-08-08 14:15 ` Paul Moore [this message]
2008-08-08 17:26 ` Joshua Brindle
2008-08-14 16:30 ` Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200808081015.19599.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=jmorris@namei.org \
--cc=mra@hp.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.