From: Ole Kliemann <ole@plastictree.net>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, Eric Paris <eparis@redhat.com>
Subject: Re: SELinux performance depending on type count
Date: Fri, 10 Aug 2012 17:43:45 +0200 [thread overview]
Message-ID: <20120810154345.GG2296@telvanni> (raw)
In-Reply-To: <1344611147.10631.65.camel@moss-pluto.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]
On Fri, Aug 10, 2012 at 11:05:47AM -0400, Stephen Smalley wrote:
> On Fri, 2012-08-10 at 16:36 +0200, Ole Kliemann wrote:
> > So we have choke_u:choke_r:choke_t. Although all other types are
> > in choke_r, that alone causes nothing. But as soon as there are
> > these 1000 attributes on choke_t the fun starts. Actually you
> > don't even need the 1000 types. Just 1000 attributes on one type
> > produces a measurable slowdown (7sec) and lags. Having 1000 types
> > beside just makes it a lot worse. But there absolutely no
> > slowdown with just 1000 types and no attributes.
>
> Interesting. We would expect some slowdown on an AVC cache miss in that
> situation, although the amount seems troubling. Things to consider:
> - Does the AVC cache need to be increased or otherwise tuned? You can
> see some information via the avcstat utility or by directly looking
> at /sys/fs/selinux/avc.
Just having 'avcstat 3' running and peeping at it:
calling 'id' without lag takes about 400 lookups, all in cache.
If I reload the policy, the first call to 'id' lags for maybe
500ms. avcstat shows for that period 400 lookups and maybe 20
misses.
Consequent calls to id do not lag and have no misses.
About the same is for 'ls ~'
But: calling 'id' from a not attribute-spammed domain after
reload shows about 5 misses too. But there is absolutely no lag.
>
> - Does security_compute_av(), which is called on a cache miss, need some
> profiling and tuning? Particularly the logic within
> context_struct_compute_av(), where we are iterating through the type
> attribute ebitmaps.
>
> In Fedora 17, most types only have a few attributes (as shown by seinfo
> -t -x). unconfined_t has a larger number of attributes than most, but
> even it only has 46 attributes. So we likely don't see this behavior
> there.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-08-10 15:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 13:02 SELinux performance depending on type count Ole Kliemann
2012-08-07 14:12 ` David Quigley
2012-08-07 17:07 ` William Roberts
2012-08-07 17:36 ` Daniel J Walsh
2012-08-08 20:44 ` Ole Kliemann
2012-08-09 10:45 ` Adam Tkac
2012-08-09 11:56 ` Ole Kliemann
2012-08-10 12:11 ` Ole Kliemann
2012-08-10 13:00 ` Stephen Smalley
2012-08-10 14:36 ` Ole Kliemann
2012-08-10 15:05 ` Stephen Smalley
2012-08-10 15:43 ` Ole Kliemann [this message]
2012-08-10 15:44 ` Ole Kliemann
2012-08-10 16:08 ` Stephen Smalley
2012-08-10 16:18 ` Stephen Smalley
2012-08-10 17:00 ` Ole Kliemann
2012-08-10 18:08 ` Stephen Smalley
2012-08-10 18:46 ` Ole Kliemann
2012-08-10 18:55 ` Stephen Smalley
2012-08-10 19:11 ` Ole Kliemann
2012-08-10 19:19 ` Stephen Smalley
2012-08-10 19:26 ` Ole Kliemann
2012-08-10 19:50 ` Stephen Smalley
2012-08-10 21:38 ` Ole Kliemann
2012-08-13 12:35 ` Stephen Smalley
2012-08-27 15:28 ` Ole Kliemann
2012-08-27 16:24 ` 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=20120810154345.GG2296@telvanni \
--to=ole@plastictree.net \
--cc=eparis@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.