public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug nptl/4578] New: Assertion `...r_state == RT_CONSISTENT' failed!
@ 2007-05-31 18:58 larry dot stewart at sicortex dot com
  2007-05-31 19:00 ` [Bug nptl/4578] " larry dot stewart at sicortex dot com
                   ` (3 more replies)
  0 siblings, 4 replies; 8+ messages in thread
From: larry dot stewart at sicortex dot com @ 2007-05-31 18:58 UTC (permalink / raw)
  To: glibc-bugs

We hit an assertion in ld.so about every 6000 runs of the cluster manager
slurmstepd on SiCortex hardware.  This is evidently the same bug as

http://www.redhat.com/archives/phil-list/2003-December/msg00008.html

Evidently it has reappeared because of ld.so consistency checking and 
because our chip (6 way SMP at 500 MHz) has a wider window of vulnerability.

We've adapted the previously reported test case so that it fails about half the
time (attached) and developed a patch (attached) that resolves the problem.

The test case doesn't fail for us on opterons, the only other systems we have
available.

The failure message we get on our machines is:

Inconsistency detected by ld.so: dl-open.c: 215: dl_open_worker: Assertion
`_dl_debug_initialize (0, args->nsid)->r_state == RT_CONSISTENT' failed!

Details:

If a thread happens to hold dl_load_lock and have r_state set to RT_ADD or
RT_DELETE at the time another thread calls fork(), then the child exit code
from fork (in nptl/sysdeps/unix/sysv/linux/fork.c in our case) re-initializes
dl_load_lock but does not restore r_state to RT_CONSISTENT. If the child
subsequently requires ld.so functionality before calling exec(), then the
assertion will fire.

The patch acquires dl_load_lock on entry to fork() and releases it on exit
from the parent path.  The child path is initialized as currently done.
This is essentially pthreads_atfork, but forced to be first because the
acquisition of dl_load_lock must happen before malloc_atfork is active
to avoid a deadlock.

-- 
           Summary: Assertion `...r_state == RT_CONSISTENT' failed!
           Product: glibc
           Version: 2.3.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
        AssignedTo: drepper at redhat dot com
        ReportedBy: larry dot stewart at sicortex dot com
                CC: glibc-bugs at sources dot redhat dot com
  GCC host triplet: mips64-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=4578

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 8+ messages in thread
[parent not found: <bug-4578-131@http.sourceware.org/bugzilla/>]
end of thread, other threads:[~2015-09-15  1:43 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-31 18:58 [Bug nptl/4578] New: Assertion `...r_state == RT_CONSISTENT' failed! larry dot stewart at sicortex dot com
2007-05-31 19:00 ` [Bug nptl/4578] " larry dot stewart at sicortex dot com
2007-05-31 19:09 ` larry dot stewart at sicortex dot com
2007-06-08 17:49 ` pasky at suse dot cz
2007-06-08 18:13 ` larry dot stewart at sicortex dot com
     [not found] <bug-4578-131@http.sourceware.org/bugzilla/>
2012-12-19 10:41 ` schwab@linux-m68k.org
2015-09-15  1:41 ` gautamshruti66 at gmail dot com
2015-09-15  1:43 ` gautamshruti66 at gmail dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).