Bug 61117 - Race condition between nss/dlopen/thread
Summary: Race condition between nss/dlopen/thread
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: 61590
TreeView+ depends on / blocked
 
Reported: 2002-03-13 20:52 UTC by hjl
Modified: 2016-11-24 14:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-03-26 16:51:47 UTC
Embargoed:


Attachments (Terms of Use)
A testcase (1.10 KB, text/plain)
2002-03-13 20:53 UTC, hjl
no flags Details

Description hjl 2002-03-13 20:52:51 UTC
There is a race condition between nss/dlopen/thread. The problem is

1. Thread A has called dlopen, and the global static initialiser inside
the shared object that's being dlopened is trying to call getservbyname
It's holding the dlopen lock, and trying to acquire the NSS lock.
2. Thread B also calls getservbyname, so we're holding the NSS lock 
(which thread A is trying to acquire), and NSS is trying to dlopen a
shared library. 

Now. We're deadlocked, because we're trying to acquire the dlopen lock,
which is held by thread A. This is obviously quite sensitive to timing.

Since NSS also does dlopen, I think it should share locks with dlopen.

Comment 1 hjl 2002-03-13 20:53:32 UTC
Created attachment 48424 [details]
A testcase

Comment 2 Jakub Jelinek 2002-04-08 13:31:49 UTC
See http://sources.redhat.com/ml/libc-alpha/2002-03/msg00053.html
I agree with Ulrich here, so WONTFIX.


Note You need to log in before you can comment on or make changes to this bug.