public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "larry dot stewart at sicortex dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/4578] New: Assertion `...r_state == RT_CONSISTENT' failed! Date: Thu, 31 May 2007 18:58:00 -0000 [thread overview] Message-ID: <20070531185841.4578.larry.stewart@sicortex.com> (raw) 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.
next reply other threads:[~2007-05-31 18:58 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-31 18:58 larry dot stewart at sicortex dot com [this message] 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
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=20070531185841.4578.larry.stewart@sicortex.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).