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

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

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

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, release/2.23/master has been updated
       via  2143af6a47027c48d8dc168e255d8f527377bc56 (commit)
      from  a37d61a662027a5d92fa54ceb75cd3167d732b5f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2143af6a47027c48d8dc168e255d8f527377bc56

commit 2143af6a47027c48d8dc168e255d8f527377bc56
Author: Florian Weimer <fweimer@redhat.com>
Date:   Thu May 12 08:54:17 2016 +0200

    Increase fork signal safety for single-threaded processes [BZ #19703]

    This provides a band-aid and addresses the scenario where fork is
    called from a signal handler while the process is in the malloc
    subsystem (or has acquired the libio list lock).  It does not
    address the general issue of async-signal-safety of fork;
    multi-threaded processes are not covered, and some glibc
    subsystems have fork handlers which are not async-signal-safe.

    (cherry picked from commit 56290d6e762c1194547e73ff0b948cd79d3a1e03)

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                |   10 ++
 malloc/Makefile          |    3 +-
 malloc/tst-mallocfork2.c |  212 ++++++++++++++++++++++++++++++++++++++++++++++
 sysdeps/nptl/fork.c      |   53 ++++++++---
 4 files changed, 262 insertions(+), 16 deletions(-)
 create mode 100644 malloc/tst-mallocfork2.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.