public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Deleted branch azanella/bz24595
Date: Thu, 08 Aug 2019 20:20:00 -0000	[thread overview]
Message-ID: <20190808202007.19500.qmail@sourceware.org> (raw)

The branch 'azanella/bz24595' was deleted.
It previously pointed to:

 88820cb... nptl: Fix deadlock on atfork handler which calls dlclose (B

Diff:

!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------

  88820cb... nptl: Fix deadlock on atfork handler which calls dlclose (B

commit 88820cb4c34f77805be822c5f090e9f1b75e1df4
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Fri Jul 12 14:33:37 2019 -0300

    nptl: Fix deadlock on atfork handler which calls dlclose (BZ#24595)
    
    Some real-world cases rely upon that atfork handlers can call functions
    that might change the atfork handlers, such as dlclose.  Since 27761a10
    (Refactor atfork handlers), all internal atfork handlers access is
    protected with a simple lock, not allowing reentrancy.  This leads to
    deadlocks for the aforementioned scenario. Although this specific usage
    is far from portable (as comment #2 in the bug report), glibc did allow
    it.
    
    This patch fixes by using a double-linked lists along with a lock
    release while calling the atfork handlers.


                 reply	other threads:[~2019-08-08 20:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190808202007.19500.qmail@sourceware.org \
    --to=azanella@sourceware.org \
    --cc=glibc-cvs@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: link
Be 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).