From owner-freebsd-current@FreeBSD.ORG Tue Oct 12 09:02:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB79916A4CF for ; Tue, 12 Oct 2004 09:02:55 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D41643D3F for ; Tue, 12 Oct 2004 09:02:55 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i9C91KYU064008; Tue, 12 Oct 2004 05:01:20 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9C91ADK064002; Tue, 12 Oct 2004 05:01:20 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 12 Oct 2004 05:01:10 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Marc UBM Bocklet In-Reply-To: <20041011220159.733ad3ce.ubm@u-boot-man.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: [BETA7-panic] sodealloc(): so_count 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 09:02:55 -0000 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... > > > > > > 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