From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: Can we eliminate or optimize nodups_specs within libselinux
Date: Wed, 1 Jun 2011 10:04:17 -0400 [thread overview]
Message-ID: <4DE646E1.1000309@tresys.com> (raw)
In-Reply-To: <4DE6430B.8080604@redhat.com>
On 06/01/11 09:47, Daniel J Walsh wrote:
> On 06/01/2011 09:41 AM, Daniel J Walsh wrote:
>> > We are costing boot 1.5s
>> >
>> > https://bugzilla.redhat.com/show_bug.cgi?id=709014
>
> This seems to be something libsemanage should do to verify the
> file_context file is good, but libselinux should just figure the
> file_context file is sane. And be optimised to read access.
Makes sense. It probably should have been doing this for a long time
anyway, since it needs to take into account for genhomedircon output and
local file contexts. I think it should also cause a transaction fail if
there are file context errors.
> Might be a reason tools like install run slow also.
I'd bet on it, since all those tools do is, basically, matchpathcon()
then setfscreatecon().
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
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.
prev parent reply other threads:[~2011-06-01 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 13:41 Can we eliminate or optimize nodups_specs within libselinux Daniel J Walsh
2011-06-01 13:47 ` Daniel J Walsh
2011-06-01 14:04 ` Christopher J. PeBenito [this message]
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=4DE646E1.1000309@tresys.com \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.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.