All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: mm19827 <mm19827@gmail.com>,
	SELinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: selinux and thread local storage
Date: Tue, 14 Apr 2015 15:57:39 -0400	[thread overview]
Message-ID: <552D7133.1040503@tycho.nsa.gov> (raw)
In-Reply-To: <loom.20150414T202953-219@post.gmane.org>

On 04/14/2015 02:45 PM, mm19827 wrote:
> Hi all,
> 
> I am trying to figure out something about Red Hat Bugzilla – Bug 1195074,
> where nvidia libGL.so.304.125 hangs in an endless loop when loaded by
> gnome-shell 3.14.
> 
> Sequence is: gnome-shell loads libGL.so which for some reason calls
> is_selinux_enabled in libselinux.so at library load time, which runs into a
> spinlock within init_thread_destructor when accessing the thread-local
> variable destructor_initialized.
> 
> gdb print of destructor_initialized reports:
> The inferior has not yet allocated storage for thread-local variables in the
> shared library `/lib64/libselinux.so.1'
> 
> gdb backtrace is:
> 
> #0  0x0000003f12412495 in tls_get_addr_tail (ti=0x3509221f58,
> dtv=0x7ffff7f83390, the_map=0x7ffff7f9c000)
>     at dl-tls.c:751

Perhaps we could address this simply by changing is_selinux_enabled() to
use a private or inlined version of getcon_raw() that does not try to
cache the result and therefore does not rely on tls?

  reply	other threads:[~2015-04-14 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 18:45 selinux and thread local storage mm19827
2015-04-14 19:57 ` Stephen Smalley [this message]
2015-04-15 17:25   ` Daniel J Walsh
2015-04-17 12:52     ` Stephen Smalley
2015-04-16 19:56 ` mm19827

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=552D7133.1040503@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=mm19827@gmail.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.