From owner-freebsd-hackers@FreeBSD.ORG  Tue Aug 14 21:09:13 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 8E47E106564A;
	Tue, 14 Aug 2012 21:09:13 +0000 (UTC) (envelope-from jilles@stack.nl)
Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107])
	by mx1.freebsd.org (Postfix) with ESMTP id 21DD58FC0C;
	Tue, 14 Aug 2012 21:09:13 +0000 (UTC)
Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131])
	by mx1.stack.nl (Postfix) with ESMTP id 821B51DD45A;
	Tue, 14 Aug 2012 23:09:11 +0200 (CEST)
Received: by snail.stack.nl (Postfix, from userid 1677)
	id 67F842847B; Tue, 14 Aug 2012 23:09:11 +0200 (CEST)
Date: Tue, 14 Aug 2012 23:09:11 +0200
From: Jilles Tjoelker <jilles@stack.nl>
To: davidxu@freebsd.org
Message-ID: <20120814210911.GA90640@stack.nl>
References: <20120730102408.GA19983@stack.nl>
	<20120730105303.GU2676@deviant.kiev.zoral.com.ua>
	<20120805215432.GA28704@stack.nl>
	<20120806082535.GI2676@deviant.kiev.zoral.com.ua>
	<20120809105648.GA79814@stack.nl> <5029D727.2090105@freebsd.org>
	<20120814081830.GA5883@deviant.kiev.zoral.com.ua>
	<502A1788.9090702@freebsd.org>
	<20120814094111.GB5883@deviant.kiev.zoral.com.ua>
	<502A6B7A.6070504@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <502A6B7A.6070504@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-hackers@freebsd.org
Subject: Re: system() using vfork() or posix_spawn() and libthr
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 21:09:13 -0000

On Tue, Aug 14, 2012 at 11:15:06PM +0800, David Xu wrote:
> But in real word, pthread atfork handlers are not async-signal safe,
> they mostly do mutex locking and unlocking to keep consistent state,
> mutex is not async-signal safe.
> The malloc prefork and postfork handlers happen to work because I have
> some hacking code in library for malloc locks. Otherwise, you even
> can not use fork() in signal handler.

This problem was also reported to the Austin Group at
http://austingroupbugs.net/view.php?id=62

Atfork handlers are inherently async-signal-unsafe.

An interpretation was issued suggesting to remove fork() from the list
of async-signal-safe functions and add a new async-signal-safe function
_Fork() which does not call the atfork handlers.

This change will however not be in POSIX.1-2008 TC1 but only in the next
issue (SUSv5).

A slightly earlier report http://austingroupbugs.net/view.php?id=18 just
requested the _Fork() function because an existing application
deadlocked when calling fork() from a signal handler.

-- 
Jilles Tjoelker