public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xujing99 at huawei dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug admin/28331] New: Multi-threaded exec pthread_create and dlopen may cause deadlock Date: Sat, 11 Sep 2021 10:35:42 +0000 [thread overview] Message-ID: <bug-28331-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28331 Bug ID: 28331 Summary: Multi-threaded exec pthread_create and dlopen may cause deadlock Product: glibc Version: 2.35 Status: UNCONFIRMED Severity: normal Priority: P2 Component: admin Assignee: unassigned at sourceware dot org Reporter: xujing99 at huawei dot com CC: carlos at redhat dot com Target Milestone: --- after merge commit 1387ad6225c2222f027790e3f460e31aa5dd2c54, multi-threaded exec pthread_create and dlopen may cause deadlock. thread1:dlopen hold dl_load_lock and then load a dynamic library which will hold ACE_lock(defined by my self) thread2:a program hold ACE_lock and then call pthread_create=>_dl_allocate_tls_init will hold dlopen dl_load_lock in this case, it will cause deadlock. for example: thread1:dlopen => hold dl_load_lock => spawn_n => wait for hold ACE_lock thread2:spawn_n => hold ACE_lock => pthread_create => _dl_allocate_tls_init => wait for hold dl_load_lock (spawn_n is my own function) -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-09-11 10:35 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-11 10:35 xujing99 at huawei dot com [this message] 2021-09-13 2:59 ` [Bug admin/28331] " xujing99 at huawei dot com 2021-09-13 7:26 ` [Bug dynamic-link/28331] " schwab@linux-m68k.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-28331-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).