From owner-freebsd-threads@FreeBSD.ORG Thu May 25 18:13:44 2006 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 1E65216B41B; Thu, 25 May 2006 18:13:44 +0000 (UTC) (envelope-from kurt@intricatesoftware.com) Received: from mta6.srv.hcvlny.cv.net (mta6.srv.hcvlny.cv.net [167.206.4.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6BD743D76; Thu, 25 May 2006 18:13:40 +0000 (GMT) (envelope-from kurt@intricatesoftware.com) Received: from [172.16.1.72] (ool-457a77e8.dyn.optonline.net [69.122.119.232]) by mta6.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0IZU0026K2KWPP11@mta6.srv.hcvlny.cv.net>; Thu, 25 May 2006 14:12:33 -0400 (EDT) Date: Thu, 25 May 2006 14:12:32 -0400 From: Kurt Miller In-reply-to: To: Daniel Eischen Message-id: <200605251412.32677.kurt@intricatesoftware.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline References: <200605251158.34553.lists@intricatesoftware.com> User-Agent: KMail/1.9.1 Cc: freebsd-threads@freebsd.org Subject: Re: close() socket deadlocks blocked threads X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 18:13:57 -0000 On Thursday 25 May 2006 1:09 pm, Daniel Eischen wrote: > On Thu, 25 May 2006, Kurt Miller wrote: > > > Here's the other deadlock I mentioned. When a thread > > is blocked waiting for data on a socket and another > > thread closes the socket, the blocked thread remains > > blocked indefinitely. Both kse and thr have this > > issue. c_r returns with -1 errno==EBADF. Solaris > > returns with -1 errno==0. > > You should send this to -current, or -stable if it works > correctly on -current. There isn't anything we can do > in the threads libraries about this. I'm not sure what > the correct behavior should be. > Ok, thanks. I filed a kern PR instead since I don't have a -current or -stable box around to confirm. http://www.freebsd.org/cgi/query-pr.cgi?pr=97921 -Kurt