Date: Tue, 12 Oct 2004 05:01:10 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Marc UBM Bocklet <ubm@u-boot-man.de> Cc: current@freebsd.org Subject: Re: [BETA7-panic] sodealloc(): so_count 1 Message-ID: <Pine.NEB.3.96L.1041012045851.55701J-100000@fledge.watson.org> In-Reply-To: <20041011220159.733ad3ce.ubm@u-boot-man.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 11 Oct 2004, Marc UBM Bocklet wrote: > > Okay, now I do; I did a more thorough potential fix -- so if that > > worked for you, this should do the same without a socket memory leak. > > The life and times of sockets are fraught with peril... > > > > <URL:http://green.homeunix.org/~green/tcp_accept_race_crash.patch>; > > Okay, bad news: > > I just got another crash with your first patch applied, unfortunately my > roommate rebooted the server without doing a dump first or having a look > at the panic message. > > I'll try applying your latest patch and see if that fixes the problems. > If it does not, I'll get a dump and the usual ddb stuff. :-) Sounds good. I know that the problem Brian identified is a real race and a potential source of precisely the panic you were seeing. One reason I was interested in getting access to a dump from the panic, though, was to (if possible) confirm that it was *the* race causing the problem. It's a very likely candidate, but it would be good to know if we should be looking for another related race. If the code now in HEAD fixes it for you, please let me know (or if not, also :-). If it doesn't, the core would be very helpful. Thanks! Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1041012045851.55701J-100000>