Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964941AbWALBXR (ORCPT ); Wed, 11 Jan 2006 20:23:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964943AbWALBXR (ORCPT ); Wed, 11 Jan 2006 20:23:17 -0500 Received: from rwcrmhc13.comcast.net ([216.148.227.153]:62614 "EHLO rwcrmhc12.comcast.net") by vger.kernel.org with ESMTP id S964941AbWALBXQ (ORCPT ); Wed, 11 Jan 2006 20:23:16 -0500 Message-ID: <43C5B393.1010600@elegant-software.com> Date: Wed, 11 Jan 2006 20:40:35 -0500 From: Russell Leighton User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org, libc-alpha@sources.redhat.com Subject: clone() + glibc thread safe? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 428 Lines: 17 Can you safely use glibc functions in a thread safe way (e.g., malloc() and friends) from threads generated by: clone(f, stack, CLONE_FS|CLONE_FILES|CLONE_VM, t) Thx Russ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/