Date: Fri, 30 Dec 2011 16:57:54 -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: <4EFE5E12.7080103@FreeBSD.org> In-Reply-To: <4EFE5B70.9050807@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> <4EFE5B70.9050807@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/30/2011 4:46 PM, Maxim Sobolev wrote: > 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? I could also open a ticket, put all debug information collected to date in there. And encourage people to report to it once they see this warning on their system. Then it would provide more information about the exposure. It is definitely looks like locking issue somewhere, not just bad luck or flaky hardware, as we see it happening consistently on top 4 most UDP-loaded systems here, and it correlates well with the load. With my small NULL catch the machines have been running happily for a month now, so there is no visible side-effects. -Maxim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EFE5E12.7080103>