Re: selinux and thread local storage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/14/2015 03:57 PM, Stephen Smalley wrote:
> 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?
>
> _______________________________________________
> Selinux mailing list
> Selinux@xxxxxxxxxxxxx
> To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
> To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
>
>
I would be fine with that.

_______________________________________________
Selinux mailing list
Selinux@xxxxxxxxxxxxx
To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.





[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux