Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Dec 2011 16:46:40 -0800
From:      Maxim Sobolev <sobomax@FreeBSD.org>
To:        "Robert N. M. Watson" <rwatson@FreeBSD.org>
Cc:        freebsd-net@freebsd.org, "Bjoern A. Zeeb" <bz@FreeBSD.ORG>, Jack Vogel <jfvogel@gmail.com>
Subject:   Re: Panic in the udp_input() under heavy load
Message-ID:  <4EFE5B70.9050807@FreeBSD.org>
In-Reply-To: <AB3D0536-CDD7-4595-911C-7C17FE1DFB23@FreeBSD.org>
References:  <4EB804D2.2090101@FreeBSD.org> <alpine.BSF.2.00.1111071818250.4603@ai.fobar.qr> <4EB86276.6080801@sippysoft.com> <4EB86866.9060102@sippysoft.com> <alpine.BSF.2.00.1111072324340.4603@ai.fobar.qr> <4EB86FCF.3050306@FreeBSD.org> <alpine.BSF.2.00.1111080239500.1358@fledge.watson.org> <4ECEE6F0.4010301@FreeBSD.org> <F63603B1-7B35-4ECE-82E6-835CD91B93F8@FreeBSD.org> <4EFE158C.2040705@FreeBSD.org> <AB3D0536-CDD7-4595-911C-7C17FE1DFB23@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 12/30/2011 3:31 PM, Robert N. M. Watson wrote:
> Looking back at a recent post from you, it appears that you are on 8.x and not 9.x, as I had assumed form your original e-mail. The patch I was referring to in 9-CURRENT has long since been merged for 9.0 and will appear in that release. However, it does not apply to 8.x, as the bug it fixed was introduced during the 9.x cycle. We'll need to do a from-scratch diagnosis here rather than assume it's the same problem. Could I ask you to follow up to this post with version information, stack traces from relevant threads, etc? I am not aware of any other reports of UDP-related crashes along the lines of what you've described in 8.x, so it may be being triggered by some unusual aspect of your workload (or just bad luck). Sorry that there's no instant "merge a patch" fix for this one.

I see. Would you guys mind if I put that NULL pointer check into the 
code for the time being and turn it into some kind of big nasty warning 
in 8-stable branch only? As far as I can tell, the most harm it can do 
is some memory being leaked. And this condition happens just few times a 
day, so it's not a biggie.

By the way it would be interesting project to put libexecinfo interface 
into the FreeBSD kernel. It would provide interesting new aspect of 
debugging such rare non-critical conditions by dumping stack traces and 
possibly doing some damage control instead of plainly crashing.

-Maxim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EFE5B70.9050807>