From: Ivan Gyurdiev <ivg2@cornell.edu>
To: selinux@tycho.nsa.gov
Cc: Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [ SEMANAGE ] Resync to sepol changes
Date: Sat, 22 Oct 2005 17:38:08 -0400 [thread overview]
Message-ID: <435AB140.4020001@cornell.edu> (raw)
In-Reply-To: <435A8AE9.3020709@cornell.edu>
>
> It _should_ commit the users file successfully... but it doesn't yet -
> need to do some more investigation.
> I'm pretty sure it's read successfully, updated successfully, and
> merged into policy... not sure why it doesn't commit.
I see what's wrong... my implementations of add() and modify() invoke
other functions of the database, but the enter_ro/exit_ro/enter_rw
functions are not reentrant. As a result, the read lock is dropped
early, and more importantly, the cache is dropped too (so all
modifications are lost every time).
Hmm...
--
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-10-22 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 18:54 [ SEMANAGE ] Resync to sepol changes Ivan Gyurdiev
2005-10-22 20:03 ` lyris test Remmolt Zwartsenberg
2005-10-22 21:38 ` Ivan Gyurdiev [this message]
2005-10-24 15:10 ` [ SEMANAGE ] Resync to sepol changes Ivan Gyurdiev
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=435AB140.4020001@cornell.edu \
--to=ivg2@cornell.edu \
--cc=sds@tycho.nsa.gov \
--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.