From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <stephen.smalley@gmail.com>
Cc: James Morris <jmorris@namei.org>,
Vesa-Matti J Kari <vmkari@cc.helsinki.fi>,
Eric Paris <eparis@parisplace.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov
Subject: Re: [patch] SELinux: trivial, unify iterator variable naming, part 3
Date: Sat, 26 Jul 2008 10:23:08 -0400 [thread overview]
Message-ID: <200807261023.09091.paul.moore@hp.com> (raw)
In-Reply-To: <1217033137.14295.11.camel@sulphur>
On Friday 25 July 2008 8:45:26 pm Stephen Smalley wrote:
> On Sat, 2008-07-26 at 00:47 +1000, James Morris wrote:
> > 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).
>
> No - the whole point of that config option is to avoid breakage on
> Fedora 3 and 4, as noted in the help text. And the option on which
> it depends defaults to n and thus shouldn't be enabled for anyone by
> default.
>
> As to whether or not we need to care about Fedora 3 and 4 anymore is
> perhaps a reasonable question; if not, then the entire option could
> go away.
I'm thinking of Andrew Morton's crufty old Fedora Core 2 laptop right
now ...
--
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-07-26 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 23:24 [patch] SELinux: trivial, unify iterator variable naming, part 3 Vesa-Matti J Kari
2008-07-24 13:28 ` James Morris
2008-07-24 16:00 ` Vesa-Matti J Kari
2008-07-25 1:20 ` Stephen Smalley
2008-07-25 13:03 ` James Morris
2008-07-25 13:19 ` Stephen Smalley
2008-07-25 14:47 ` James Morris
2008-07-26 0:45 ` Stephen Smalley
2008-07-26 14:23 ` Paul Moore [this message]
2008-07-28 18:13 ` 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=200807261023.09091.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=stephen.smalley@gmail.com \
--cc=vmkari@cc.helsinki.fi \
/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.