Date: Tue, 5 Jun 2012 08:48:48 +0200 (CEST) From: Joerg Pulz <Joerg.Pulz@frm2.tum.de> To: Daniel Hartmeier <daniel@benzedrine.cx> Cc: bug-followup@freebsd.org, freebsd-pf@freebsd.org Subject: Re: kern/168190: [pf] panic when using pf and route-to (maybe: bad fragment handling?) Message-ID: <alpine.BSF.2.00.1206050845350.89783@unqrf.nqzva.sez2> In-Reply-To: <20120604102544.GC13069@insomnia.benzedrine.cx> References: <201205271830.q4RIU9fA039893@freefall.freebsd.org> <20120529064910.GA12508@insomnia.benzedrine.cx> <alpine.BSF.2.00.1206011015290.89783@unqrf.nqzva.sez2> <20120604065344.GA13069@insomnia.benzedrine.cx> <20120604100829.GB13069@insomnia.benzedrine.cx> <20120604102544.GC13069@insomnia.benzedrine.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 4 Jun 2012, Daniel Hartmeier wrote: > Here's a patch that directly tests this theory. > > If correct, it will replace the panics with simple log messages that > show when ipfilter left an m_len==0 mbuf. Daniel, seems that your patch fixed it. I've seen the following log entry: Jun 5 02:15:33 charon kernel: fr_check_wrapper: m_len 0 fixed No panic and everything is running smooth. I will go and recompile the kernel with all the IPFIREWALL options reenabled to make sure that the byte ordering problem does not appear. I will report back. Thanks for your help. Joerg - -- The beginning is the most important part of the work. -Plato -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iD8DBQFPzavTSPOsGF+KA+MRArY+AJ43yqTeJ6hb+uCM7xZ8FWTztCz69ACgg1Wx yVCCuNUO0ipvlbPwa0jzZjM= =MGzr -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1206050845350.89783>