From: Joshua Brindle <jbrindle@tresys.com>
To: gyurdiev@redhat.com
Cc: selinux@tycho.nsa.gov
Subject: Re: [ libsepol 0/6] Context reorganization
Date: Fri, 22 Jul 2005 10:03:00 -0400 [thread overview]
Message-ID: <42E0FC94.2060501@tresys.com> (raw)
In-Reply-To: <1122040159.24847.10.camel@celtics.boston.redhat.com>
Ivan Gyurdiev wrote:
>On Thu, 2005-07-21 at 14:14 -0400, Ivan Gyurdiev wrote:
>
>
>>>well, that is because the cache bitmap is empty. I'm not sure exactly
>>>what the order you do things in but you'll need to either call
>>>policydb_index_others after you've loaded all the users
>>>
>>>
>>I specifically don't want to do that - that's why I use realloc
>>and index users one by one...
>>
>>Notice how the new API deals with single users, and
>>does not provide a way to load many users at once.
>>It's supposed to be used as part of an iterator
>>in libsemanage, and I don't want to loop over
>>the entire set of users every time I modify a single
>>one.
>>
>>
>
>Also, correct me if I'm wrong, but I don't think sepol_genusers_policydb
>ever calls index_others either - it calls reindex_users directly.
>
>
>
>Does that mean that this cache business breaks sepol_genusers_policydb
>as is? Not sure how important that is, given that this function is never
>actually exported via the shared API...
>
>
it also doesn't call context_isvalid() which means it doesn't need the
cache.
--
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:[~2005-07-22 14:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 17:31 [ libsepol 0/6] Context reorganization Ivan Gyurdiev
2005-07-21 18:00 ` Joshua Brindle
2005-07-21 18:03 ` Ivan Gyurdiev
2005-07-21 18:09 ` Joshua Brindle
2005-07-21 18:14 ` Ivan Gyurdiev
2005-07-22 13:49 ` Ivan Gyurdiev
2005-07-22 14:03 ` Joshua Brindle [this message]
2005-07-22 14:04 ` Ivan Gyurdiev
2005-07-22 14:11 ` Joshua Brindle
2005-07-22 14:15 ` Ivan Gyurdiev
2005-07-22 14:16 ` Ivan Gyurdiev
2005-07-22 14:25 ` Joshua Brindle
2005-07-22 14:57 ` Ivan Gyurdiev
2005-07-22 15:14 ` Joshua Brindle
[not found] ` <1122386595.4470.40.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1122387393.4470.54.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1122393674.4470.73.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1122393858.2812.5.camel@celtics.boston.redhat.com>
[not found] ` <1122395431.2812.13.camel@celtics.boston.redhat.com>
[not found] ` <1122396106.4470.76.camel@moss-spartans.epoch.ncsc.mil>
2005-07-26 16:52 ` [ libsepol 10 ] Bugfixes for 0-9 Ivan Gyurdiev
2005-07-26 17:43 ` Ivan Gyurdiev
2005-07-26 19:00 ` Stephen Smalley
2005-07-26 19:01 ` Ivan Gyurdiev
2005-07-26 19:06 ` 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=42E0FC94.2060501@tresys.com \
--to=jbrindle@tresys.com \
--cc=gyurdiev@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.