[Bug nptl/19703] New: Do not run malloc/libio fork handlers in a signal handler

["fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19703

            Bug ID: 19703
           Summary: Do not run malloc/libio fork handlers in a signal
                    handler
           Product: glibc
           Version: 2.24
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
                CC: drepper.fsp at gmail dot com
        Depends on: 19702
  Target Milestone: ---

The fork handlers for malloc and libio are clearly not async-signal-safe (they
take many locks).  But fork has to be safe to use in a signal handler.  We
should use the flag provided by bug 19702 to skip running these particular fork
handlers if we detect that we are running from a signal handler.

(Skipping fork handlers in general is not permittedâit is the responsibility of
applications to install async-signal-safe handlers if fork is called from a
signal handler.)


Referenced Bugs:

https://sourceware.org/bugzilla/show_bug.cgi?id=19702
[Bug 19702] Provide a flag indicating whether a thread is in a signal handler
-- 
You are receiving this mail because:
You are on the CC list for the bug.