From owner-freebsd-net@FreeBSD.ORG Tue Nov 8 02:41:01 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24CD5106564A; Tue, 8 Nov 2011 02:41:01 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id F2CCD8FC13; Tue, 8 Nov 2011 02:41:00 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 695F846B09; Mon, 7 Nov 2011 21:41:00 -0500 (EST) Date: Tue, 8 Nov 2011 02:41:00 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Maxim Sobolev In-Reply-To: <4EB86FCF.3050306@FreeBSD.org> Message-ID: References: <4EB804D2.2090101@FreeBSD.org> <4EB86276.6080801@sippysoft.com> <4EB86866.9060102@sippysoft.com> <4EB86FCF.3050306@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "Bjoern A. Zeeb" , Jack Vogel Subject: Re: Panic in the udp_input() under heavy load X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2011 02:41:01 -0000 On Mon, 7 Nov 2011, Maxim Sobolev wrote: > On 11/7/2011 3:25 PM, Bjoern A. Zeeb wrote: >> Now if you are clever you'd also log the inp there as the above will only >> prove the case that something is wrong but still not help us in anything to >> figure out what. > > Good point, thank you Sir. > > Would that be good enough? > > printf("BZZT! Something is terribly wrong, up == NULL! inp = %p\n", inp); > > Do you think of any other useful piece of information that I can log at this > point? Hi Maxim: There was recently a commit to fix a race condition in 10-CURRENT which I think is not slated to be merged for 9.0. You might check the commit logs there and see if that fixes the problems you have -- if so, we might want to reconsider the plan not to merge for 9.0. (It relates to a race condition on closing sockets..) Robert