From owner-freebsd-current@FreeBSD.ORG Wed Jun 15 13:11:18 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 170AA16A41F for ; Wed, 15 Jun 2005 13:11:18 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 053F843D49; Wed, 15 Jun 2005 13:11:18 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5FDBGgK049534; Wed, 15 Jun 2005 13:11:17 GMT (envelope-from davidxu@freebsd.org) Message-ID: <42B028EA.2020901@freebsd.org> Date: Wed, 15 Jun 2005 21:11:06 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.8) Gecko/20050605 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Luigi Rizzo References: <20050615025447.A62971@xorpc.icir.org> In-Reply-To: <20050615025447.A62971@xorpc.icir.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: bug or feature in userland thread library (O_NONBLOCK) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 13:11:18 -0000 Luigi Rizzo wrote: >Probably a known issue, but I thought it worthwhile reporting it, >if nothing else for archival purposes. > >I think our userland thread library (libc_r) has some bugs in >handling descriptors. I can reproduce the behaviour on -current >and 4.x, and I believe it applies to 5.x too. > >Following is a description of the problem and some code to replicate it >The code includes a workaround but it is not particularly nice. > >Any better ideas ? I am not sure on what to do, but perhaps the >only sensible thing to do is to add a note with this workaround >(or better ones, if available) to our pthreads manpage > > > libc_r is deprecated on -CURRENT, I think start from 6.0, libc_r really should be moved to ports. ;) David Xu