From owner-freebsd-threads@FreeBSD.ORG Thu May 25 17:09:20 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 8B44916A6D4 for ; Thu, 25 May 2006 17:09:20 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C314443D46 for ; Thu, 25 May 2006 17:09:19 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k4PH9IAk023316; Thu, 25 May 2006 13:09:18 -0400 (EDT) Date: Thu, 25 May 2006 13:09:18 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: kurt@intricatesoftware.com In-Reply-To: <200605251158.34553.lists@intricatesoftware.com> Message-ID: References: <200605251158.34553.lists@intricatesoftware.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) 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 Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 17:09:22 -0000 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. -- DE