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