Date: Tue, 03 Jul 2007 15:06:41 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: bu7cher@yandex.ru Cc: rwatson@freebsd.org, freebsd-current@freebsd.org Subject: Re: Panic in ipfw Message-ID: <E1I5i5Z-0006fa-VE@clue.co.za> In-Reply-To: Message from "Andrey V. Elsukov" <bu7cher@yandex.ru> of "Tue, 03 Jul 2007 16:08:47 %2B0400." <468A3C4F.000001.30479@webmail12.yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
"Andrey V. Elsukov" wrote: > Hi, Ian. > > > I got this panic yesterday on a fairly busy firewall. I have some > > private patches to ip_fw2.c and to the em driver (see the earlier > > "em0 hijacking traffic to port 623" thread). I don't think this > > panic is a result of those changes. > > > It occurred round about the time an address was added to an interface. > > I have a patch that can help you (i guess..). > Can you test this patch? > > http://butcher.heavennet.ru/patches/kernel/inaddr_locking/ Thanks. Wow, that looks like it touches a lot more than just ipfw. It took about 1.5 years of production at 2.3 billion backets a day to trigger this condition twice. It's going to be difficult to tell if this patch fixes the problem. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1I5i5Z-0006fa-VE>