From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 9 03:30:09 2009 Return-Path: Delivered-To: hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 849EF1065670; Fri, 9 Jan 2009 03:30:09 +0000 (UTC) (envelope-from green@green.homeunix.org) Received: from green.homeunix.org (green.homeunix.org [66.92.150.152]) by mx1.freebsd.org (Postfix) with ESMTP id 3C0278FC0C; Fri, 9 Jan 2009 03:30:08 +0000 (UTC) (envelope-from green@green.homeunix.org) Received: from green.homeunix.org (obama@localhost [127.0.0.1]) by green.homeunix.org (8.14.3/8.14.1) with ESMTP id n093JiIA036464; Thu, 8 Jan 2009 22:19:44 -0500 (EST) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.14.3/8.14.1/Submit) id n093Jhad036463; Thu, 8 Jan 2009 22:19:43 -0500 (EST) (envelope-from green) Date: Thu, 8 Jan 2009 22:19:43 -0500 From: Brian Fundakowski Feldman To: hackers@FreeBSD.org, jasone@FreeBSD.org Message-ID: <20090109031942.GA2825@green.homeunix.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: threaded, forked, rethreaded processes will deadlock X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2009 03:30:09 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline It appears that the post-fork hooks for malloc(3) are somewhat broken such that when a threaded program forks, and then its child attempts to go threaded, it deadlocks because it already appears to have locks held. I am not familiar enough with the current libthr/libc/rtld-elf interaction that I've been able to fix it myself, unfortunately. I discovered this today upgrading my work box from 7.0 to 7.1, but I can easily reproduce it at home on a stale -CURRENT as well. Testing on an OS X box to make sure, the regression test does exit 0 there. Has anyone happened to have fixed this already locally? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ --VbJkn9YxBvnuCH5J--