From owner-freebsd-net@FreeBSD.ORG Fri Nov 25 07:24:02 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 77701106564A; Fri, 25 Nov 2011 07:24:02 +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 4FA278FC08; Fri, 25 Nov 2011 07:24:02 +0000 (UTC) Received: from [192.168.2.115] (host86-148-124-36.range86-148.btcentralplus.com [86.148.124.36]) by cyrus.watson.org (Postfix) with ESMTPSA id 6258046B06; Fri, 25 Nov 2011 02:24:01 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <4ECEE6F0.4010301@FreeBSD.org> Date: Fri, 25 Nov 2011 07:24:00 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4EB804D2.2090101@FreeBSD.org> <4EB86276.6080801@sippysoft.com> <4EB86866.9060102@sippysoft.com> <4EB86FCF.3050306@FreeBSD.org> <4ECEE6F0.4010301@FreeBSD.org> To: Maxim Sobolev X-Mailer: Apple Mail (2.1084) 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 07:24:02 -0000 On 25 Nov 2011, at 00:53, Maxim Sobolev wrote: >> 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. >>=20 >> (It relates to a race condition on closing sockets..) >=20 > 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. Do we know if this fix has been merged to stable/9 and releng/9.0? Given = multiple reports of instability without it, I think we would be = well-served to merge it at this point. Robert=