Date: Sun, 29 Jun 2008 13:58:06 +0200 From: Ali Niknam <ali@transip.nl> To: Robert Watson <rwatson@FreeBSD.org> Cc: net@freebsd.org Subject: Re: Probably not a kernel bug (was: Re: FreeBSD 7.0: sockets stuck in CLOSED state...) Message-ID: <486778CE.4000103@transip.nl> In-Reply-To: <20080629073519.D10134@fledge.watson.org> References: <486283B0.3060805@transip.nl> <20080625195523.N29013@fledge.watson.org> <4862BCF5.4070900@transip.nl> <20080626081831.V96707@fledge.watson.org> <20080627090939.M78484@fledge.watson.org> <20080629073519.D10134@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Guys, > Another public follow-up: Ali has been sending me debugging information > privately due to the inclusion of application source code and IP > addresses. Tracing of the application suggests that there is an > application concurrency bug leading to one socket to be closed twice and > another socket to be left open. The bug might be triggering in 7.x but > not earlier releases because of the change to libthr, which can lead to > more parallelism/asynchrony in the application. > After more testing I can with almost absolute certainty conclude that it is indeed an application bug. Reasons that it did not manifest itself earlier most probably are due to the much increased performance of BSD 7, making a certain race condition likely where it once was improbable. I want to thank all who've helped track this issue down! Kind Regards, Ali
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?486778CE.4000103>