Date: Thu, 07 Jun 2007 11:19:06 -0700 From: Julian Elischer <julian@elischer.org> To: Ian FREISLICH <ianf@clue.co.za> Cc: current@freebsd.org Subject: Re: Panic in ipfw Message-ID: <46684C1A.7050809@elischer.org> In-Reply-To: <E1HwDoF-000BLX-SX@clue.co.za> References: <E1HwDoF-000BLX-SX@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian FREISLICH wrote: > Hi > > 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'll keep the crashdump around for a while in case anyone wants more data. > > FreeBSD firewall2 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Thu May 24 10:43:20 SAST 2007 ianf@firewall2:/usr/obj/usr/src/sys/FIREWALL i386 > There is no locking to say between the firewall and the interface addresses. it probably followed a bad pointer when the addresses were changed.. your bug report should say "ipfw doesn't take part in interface address locking, leading to occasional crashes" > 2929 INADDR_TO_IFP(src_ip, tif); > (kgdb) l > 2924 > 2925 case O_IP_SRC_ME: > 2926 if (is_ipv4) { > 2927 struct ifnet *tif; > 2928 > 2929 INADDR_TO_IFP(src_ip, tif); > 2930 match = (tif != NULL); > 2931 } > 2932 break; > 2933 > (kgdb) print src_ip > $1 = {s_addr = 3268032198} > (kgdb) print tif > Variable "tif" is not available. > (kgdb) print *tif > Variable "tif" is not available. > > > -- > Ian Freislich > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46684C1A.7050809>