From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Chad Sellers <csellers@tresys.com>
Cc: "'Daniel J Walsh'" <dwalsh@redhat.com>,
selinux-dev@tresys.com, Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov
Subject: Re: [PATCH] move genhomedircon call out of transaction
Date: Mon, 14 Nov 2005 22:22:53 -0500 [thread overview]
Message-ID: <4379548D.3010801@cornell.edu> (raw)
In-Reply-To: <BF9E9FD2.8085%csellers@tresys.com>
>>> Attached is a patch that moves the genhomedircon patch out of the libsemanage
>>> transaction. This is necessary since genhomedircon now uses libsemanage, and
>>> enters a transaction itself.
>>>
>>>
>> I don't think genhomedircon enters a transaction... nor should it - it's
>> a read-only operation with respect to the objects that we manage
>> (currently). I could be wrong, but I can't find where it enters a
>> transaction in the patch.
>>
> Yep it does. It calls semanage_user_list(), which calls dbase_list(), which
> calls enter_ro(), which gets the lock.
>
I see the problem now - you confused me, because that's the active lock,
not the transaction lock. It is not entering a transaction - it's
guarding against a concurrent commit, but you *are* doing a concurrent
commit, and calling genhomedircon as part of it.
>> Also, even if it did enter transaction, exiting and re-entering
>> "immediatly" would create a race condition.
>>
> Could you expand on this race condition? genhomedircon is only reading from
> libsemanage to generate file_contexts.homedir. What race condition are you
> worried about?
>
Well... any time you're releasing a lock, and you want to re-acquire it
before changes are made - that's a potential race condition. I guess in
this case you don't care if changes are made in the meantime, so there
is no race condition.
On the other hand, genhomedir called outside libsemanage has a race in
itself, because changes can be introduced between the time you call
user_list, and seuser_list. It seems you're moving the place it's called
to the end of install_sandbox (hard to tell without -p flag), so if it's
called within libsemanage, that won't be a problem (active lock
released, transaction lock still held, concurrent commit not possible).
--
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-11-15 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 22:09 [PATCH] move genhomedircon call out of transaction Chad Sellers
2005-11-14 23:02 ` Ivan Gyurdiev
2005-11-14 23:07 ` Ivan Gyurdiev
2005-11-15 1:10 ` Chad Sellers
2005-11-15 3:22 ` Ivan Gyurdiev [this message]
2005-11-15 4:02 ` Ivan Gyurdiev
2005-11-15 13:23 ` 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=4379548D.3010801@cornell.edu \
--to=ivg2@cornell.edu \
--cc=csellers@tresys.com \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux-dev@tresys.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.