All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Chad Sellers <csellers@tresys.com>
Cc: selinux@tycho.nsa.gov, method@manicmethod.com, slawrence@tresys.com
Subject: Re: [PATCH] libselinux: Export reset_selinux_config()
Date: Thu, 22 Oct 2009 14:51:45 -0400	[thread overview]
Message-ID: <4AE0A9C1.6070908@tycho.nsa.gov> (raw)
In-Reply-To: <1256052119-23845-1-git-send-email-csellers@tresys.com>

On 10/20/2009 11:21 AM, Chad Sellers wrote:
> In integrating SELinux policy into rpm, we have a need to be
> able to reset the configuration data (e.g. policy type) loaded
> into libselinux. These values are currently loaded lazily by a
> number of different functions (e.g. matchpatchcon_init()).
> Since we are changing rpm to install policy, including initial
> base policy, we need to be able to reload these configuration
> items after the policy has been installed.
>
> reset_selinux_config() already exists and is used by
> selinux_init_load_policy() for a similar reason, but it is not
> exported. This was probably intentionaly since it is not thread
> safe at all. That said, rpm needs to do the same thing. This
> patch makes the function public, and places a warning in the
> header comment that it is not thread safe.
>
> Signed-off-by:  Chad Sellers <csellers@tresys.com>
>   


FWIW, I plan to take a look at broader locking and thread-safety issues
in libselinux.



-- 

Eamon Walsh 
National Security Agency


--
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:[~2009-10-22 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 15:21 [PATCH] libselinux: Export reset_selinux_config() Chad Sellers
2009-10-22 18:51 ` Eamon Walsh [this message]
2009-10-22 18:54   ` Chad Sellers

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=4AE0A9C1.6070908@tycho.nsa.gov \
    --to=ewalsh@tycho.nsa.gov \
    --cc=csellers@tresys.com \
    --cc=method@manicmethod.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=slawrence@tresys.com \
    /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.