Date: Thu, 25 May 2006 13:09:18 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: kurt@intricatesoftware.com Cc: freebsd-threads@freebsd.org Subject: Re: close() socket deadlocks blocked threads Message-ID: <Pine.GSO.4.64.0605251307180.4165@sea.ntplx.net> In-Reply-To: <200605251158.34553.lists@intricatesoftware.com> References: <200605251158.34553.lists@intricatesoftware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0605251307180.4165>