From owner-freebsd-threads@FreeBSD.ORG Thu Jun 5 09:13:04 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E7A537B404 for ; Thu, 5 Jun 2003 09:13:04 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71FB843F75 for ; Thu, 5 Jun 2003 09:13:03 -0700 (PDT) (envelope-from eischen@pcnet.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h55GCxNc001943; Thu, 5 Jun 2003 12:12:59 -0400 (EDT) Date: Thu, 5 Jun 2003 12:12:59 -0400 (EDT) From: Daniel Eischen To: Terry Lambert In-Reply-To: <3EDF2C6B.7A8E5C21@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Kern Sibbald cc: freebsd-threads@freebsd.org Subject: Re: FreeBSD pthread_equal "bug" X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2003 16:13:04 -0000 On Thu, 5 Jun 2003, Terry Lambert wrote: > Daniel Eischen wrote: > > Process id's can wrap around so it can eventually happen. > > > > This is a bug in the application; the implementation is allowed > > to reuse thread id's and there are enough interfaces for an > > application to tell when a thread terminates (pthread_join). > > > > Perhaps our use of thread id's could be changes so that they > > were cached at the end of the free thread list, but cacheing > > them at the front seems to highlight bad applications, so > > that's a bonus ;-) > > So's not explicitly protecting dlopen(), and so's not forcing I never committed anything that protected dlopen(), and > rescheduling of the thread that was running at preemption time, > when returning from an involuntary preemption. ;^). also never committed anything to do this either. The rtld-elf fixes were not specifically related to dlopen(). Binding of objects was not thread-safe even if dlopen() was not used. -- Dan Eischen