public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/27054] New: pthread_atfork handlers that call pthread_atfork deadlock Date: Fri, 11 Dec 2020 15:26:24 +0000 [thread overview] Message-ID: <bug-27054-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27054 Bug ID: 27054 Summary: pthread_atfork handlers that call pthread_atfork deadlock Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: fweimer at redhat dot com CC: drepper.fsp at gmail dot com Target Milestone: --- Flags: security- Some applications call pthread_atfork from a pthread_atfork handler in the new subprocess because POSIX does not specify that the handlers are duplicated by fork. With the current implementation, this results in a deadlock. We must not call pthread_atfork handlers while holding implementation locks. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-12-11 15:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-11 15:26 fweimer at redhat dot com [this message] 2020-12-11 15:31 ` [Bug libc/27054] " fweimer at redhat dot com 2020-12-15 16:37 ` adhemerval.zanella at linaro dot org 2020-12-15 16:46 ` fweimer at redhat dot com 2022-05-25 9:31 ` cvs-commit at gcc dot gnu.org 2022-05-30 11:39 ` cvs-commit at gcc dot gnu.org 2022-05-30 15:45 ` cvs-commit at gcc dot gnu.org 2022-05-31 16:24 ` arjun.is at lostca dot se
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-27054-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).