From owner-freebsd-net@FreeBSD.ORG Fri Nov 25 00:53:12 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 DA16A1065670; Fri, 25 Nov 2011 00:53:12 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail.sippysoft.com (mail.sippysoft.com [4.59.13.245]) by mx1.freebsd.org (Postfix) with ESMTP id 9ECCB8FC14; Fri, 25 Nov 2011 00:53:12 +0000 (UTC) Received: from s0106005004e13421.vs.shawcable.net ([70.71.175.212] helo=[192.168.1.79]) by mail.sippysoft.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1RTk2R-000IkP-7P; Thu, 24 Nov 2011 16:53:11 -0800 Message-ID: <4ECEE6F0.4010301@FreeBSD.org> Date: Thu, 24 Nov 2011 16:53:04 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Robert Watson References: <4EB804D2.2090101@FreeBSD.org> <4EB86276.6080801@sippysoft.com> <4EB86866.9060102@sippysoft.com> <4EB86FCF.3050306@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: sobomax@sippysoft.com X-ssp-trusted: yes 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: Fri, 25 Nov 2011 00:53:12 -0000 On 11/7/2011 6:41 PM, Robert Watson wrote: > > 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..) Hi Robert, Thank you for the tip. I will give it a try and see what happens. So far, after installing that trap we have not seen any panics yet. I have not checked logs yet if my trap actually has catch anything or not. -Maxim