From: Ivan Gyurdiev <ivg231@gmail.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: libsemage patch to not compile modules for seusers and fcontext
Date: Thu, 14 Aug 2008 21:38:50 -0400 [thread overview]
Message-ID: <48A4DE2A.3090002@gmail.com> (raw)
In-Reply-To: <48A48B8C.3070908@redhat.com>
Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Patch speeds up semanage command from 17-20 seconds to 3-4 seconds.
>
Hi Dan!
Some suggestions below, if I can still remember correctly how this was
supposed to work:
One issue with the patch is that it makes an already large and hard to
maintain function even larger - it would be better to split it up and
make it modular instead. Likely "merge_components" and
"commit_components" should be changed to pass the components to merge or
commit as arguments - so you can operate on file and policydb components
separately.
The "attach" calls shouldn't really be needed, since you're not
re-writing the policydb, or changing ports/bools/etc. It would be better
to change the rest of the code, so that the attach calls become
unnecessary in this code path.
On the other hand the code that parses out seusers/fcontexts/users_extra
info from the module package may be necessary, so that your local
seusers/fcontexts/users_extra changes are properly merged with the
shipped policy files - these are the "write_file" sections above.
- Ivan
--
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-15 1:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 19:46 libsemage patch to not compile modules for seusers and fcontext Daniel J Walsh
2008-08-15 1:38 ` Ivan Gyurdiev [this message]
2008-08-22 13:38 ` Stephen Smalley
2008-08-26 15:11 ` Daniel J Walsh
2008-08-26 15:28 ` Joshua Brindle
2008-08-26 17:26 ` Daniel J Walsh
2008-08-26 18:42 ` Joshua Brindle
2008-08-27 1:52 ` Ivan Gyurdiev
2008-08-27 12:04 ` Stephen Smalley
2008-08-27 22:44 ` Joshua Brindle
2008-08-27 22:55 ` Joshua Brindle
2008-09-04 15:16 ` Joshua Brindle
2008-09-04 19:16 ` Daniel J Walsh
2008-09-05 2:52 ` Ivan Gyurdiev
2008-09-10 14:30 ` Daniel J Walsh
2008-09-11 3:08 ` Ivan Gyurdiev
2008-09-12 18:53 ` Joshua Brindle
2008-09-15 12:53 ` Daniel J Walsh
2008-09-15 15:59 ` Joshua Brindle
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=48A4DE2A.3090002@gmail.com \
--to=ivg231@gmail.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.