public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "macro@linux-mips.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/15686] New: Shared-object static constructors called with a lock held Date: Wed, 26 Jun 2013 22:43:00 -0000 [thread overview] Message-ID: <bug-15686-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15686 Bug ID: 15686 Summary: Shared-object static constructors called with a lock held Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: macro@linux-mips.org CC: macro@linux-mips.org Target: *-*-* Shared-object static constructors are user code that the C library has no control of. They are called with the GL(dl_load_lock) lock held and are therefore prone to a deadlock if they call back into the wrong part of ld.so. The exact call sequence is: _dl_open -> dl_open_worker -> _dl_init -> call_init -> user code and in the sequence above _dl_open takes the GL(dl_load_lock) lock before calling dl_open_worker. This affects all targets. See also: http://sourceware.org/ml/libc-alpha/2013-06/msg00802.html http://sourceware.org/ml/libc-alpha/2013-06/msg00828.html -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-06-26 22:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-26 22:43 macro@linux-mips.org [this message] 2014-06-13 13:30 ` [Bug dynamic-link/15686] " fweimer at redhat dot com 2021-09-13 12:41 ` nsz at gcc dot gnu.org 2021-09-21 13:21 ` nsz at gcc dot gnu.org
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=bug-15686-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).