Date: Wed, 7 Jun 2006 14:34:53 GMT From: Robert Watson <rwatson@FreeBSD.org> To: rwatson@FreeBSD.org, freebsd-bugs@FreeBSD.org, rwatson@FreeBSD.org Subject: Re: kern/97921: close() socket deadlocks blocked threads Message-ID: <200606071434.k57EYrxn036670@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Synopsis: close() socket deadlocks blocked threads Responsible-Changed-From-To: freebsd-bugs->rwatson Responsible-Changed-By: rwatson Responsible-Changed-When: Wed Jun 7 14:30:14 UTC 2006 Responsible-Changed-Why: Grab ownership of this PR. This is a somewhat complicated issue to address, as socket shutdown occurs only once the last user space reference to the socket is released. This occurs when the last outstanding system call after close() takes place. To change this, we will need to change the socket state engine some to issue a cancellation on last close rather than last reference, which is a notion we sort of (but not entirely) support. Are there any standards that specify this or related behavior that we should be aware of? http://www.freebsd.org/cgi/query-pr.cgi?pr=97921
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606071434.k57EYrxn036670>