All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: SELinux <selinux@tycho.nsa.gov>
Subject: Re: Can we eliminate or optimize nodups_specs within libselinux
Date: Wed, 01 Jun 2011 09:47:55 -0400	[thread overview]
Message-ID: <4DE6430B.8080604@redhat.com> (raw)
In-Reply-To: <4DE64180.50302@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

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.

Might be a reason tools like install run slow also.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk3mQwsACgkQrlYvE4MpobMxHwCghBRuPpL2c8wGITLeF6jAGRsO
3yUAnimXDBNaeM4aNYuVQSv7zBOaigmF
=9XXq
-----END PGP SIGNATURE-----

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

  reply	other threads:[~2011-06-01 13:47 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 [this message]
2011-06-01 14:04   ` Christopher J. PeBenito

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=4DE6430B.8080604@redhat.com \
    --to=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.