Date: Fri, 28 May 2010 04:40:03 GMT From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov> To: freebsd-net@FreeBSD.org Subject: Re: kern/146845: [libc] close(2) returns error 54 (connection reset by peer) wrongly Message-ID: <201005280440.o4S4e3sM052201@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/146845; it has been noted by GNATS. From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov> To: "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.org> Cc: Subject: Re: kern/146845: [libc] close(2) returns error 54 (connection reset by peer) wrongly Date: Fri, 28 May 2010 00:07:16 -0400 Hi Mikolaj and Robert, Thanks for following up on this issue! > It looks like SO_LINGER is not important to reproduce ECONNRESET. Indeed, it is not. > I am attaching the patch, which may not be a solution IMHO, it is not, unfortunately, a solution: it seems to clear ECONNRESET blindly and w/o distinguishing the situation when the remote end closes the connection prematurely (i.e. before acknowledging all data written from the local end) -- and that qualifies for the true "connection reset by peer" from close()... Anton Lavrentiev Contractor NIH/NLM/NCBI
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201005280440.o4S4e3sM052201>