From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1940 invoked by alias); 1 Apr 2004 07:50:27 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 1924 invoked from network); 1 Apr 2004 07:50:27 -0000 Received: from unknown (HELO palrel10.hp.com) (156.153.255.245) by sources.redhat.com with SMTP; 1 Apr 2004 07:50:27 -0000 Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel10.hp.com (Postfix) with ESMTP id CA7F01C0111B for ; Wed, 31 Mar 2004 23:50:26 -0800 (PST) Received: from napali.hpl.hp.com (napali.hpl.hp.com [15.4.89.123]) by hplms2.hpl.hp.com (8.12.10/8.12.10/HPL-PA Hub) with ESMTP id i317oPcb001926 for ; Wed, 31 Mar 2004 23:50:25 -0800 (PST) Received: from napali.hpl.hp.com (napali [127.0.0.1]) by napali.hpl.hp.com (8.12.11/8.12.11/Debian-1) with ESMTP id i317oPAx007690 for ; Wed, 31 Mar 2004 23:50:25 -0800 Received: (from davidm@localhost) by napali.hpl.hp.com (8.12.11/8.12.11/Debian-1) id i317oP2j007686; Wed, 31 Mar 2004 23:50:25 -0800 From: David Mosberger MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16491.51649.225477.81600@napali.hpl.hp.com> Date: Thu, 01 Apr 2004 07:50:00 -0000 To: libc-hacker@sources.redhat.com Subject: is dl_iterate_phdr() supposed to be async-signal safe? Reply-To: davidm@hpl.hp.com X-URL: http://www.hpl.hp.com/personal/David_Mosberger/ X-SW-Source: 2004-04/txt/msg00001.txt.bz2 Subject pretty much says it all: I thought it was meant to be async-signal safe but looking at the __pthread_mutex_lock() code, it pretty clearly can't be, since it's updating the count and ownership members non-atomically with respect to signal-delivery. Or am I missing something? So much for dl_iterate_phdr() being an "obvious" interface... ;-/ --david