[Bug libc/12847] dprintf/vdprintf can cause fork to fail (child process crash)

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

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

--- Comment #7 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, master has been updated
       via  217a74a85cdd60df236c296ad88142b78d35eccf (commit)
      from  aa76a5c7010e98c737d79f37aa6ae668f60f7a00 (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=217a74a85cdd60df236c296ad88142b78d35eccf

commit 217a74a85cdd60df236c296ad88142b78d35eccf
Author: Andreas Schwab <schwab@suse.de>
Date:   Mon Dec 8 15:13:38 2014 +0100

    Don't touch user-controlled stdio locks in forked child (bug 12847)

    The stdio locks for streams with the _IO_USER_LOCK flag should not be
    touched by internal code.

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

Summary of changes:
 ChangeLog           |    6 ++++++
 sysdeps/nptl/fork.c |    3 ++-
 2 files changed, 8 insertions(+), 1 deletions(-)

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