kern/168190: [pf] panic when using pf and route-to (maybe: bad fragment handling?)

[Joerg Pulz]

The following reply was made to PR kern/168190; it has been noted by GNATS.

From: Joerg Pulz <Joerg.Pulz at frm2.tum.de>
To: Daniel Hartmeier <daniel at benzedrine.cx>
Cc: bug-followup at freebsd.org, freebsd-pf at freebsd.org
Subject: Re: kern/168190: [pf] panic when using pf and route-to (maybe: bad
 fragment handling?)
Date: Tue, 5 Jun 2012 14:41:20 +0200 (CEST)

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 
 On Tue, 5 Jun 2012, Joerg Pulz wrote:
 
 > 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.
 
 Daniel,
 
 as promised here is my report.
 
 Your patch resolved all problems and panics.
 I've seen two log entries since i reenabled all IPFIREWALL options.
 
 Jun  5 14:07:19 charon kernel: fr_check_wrapper: m_len 0 fixed
 Jun  5 14:07:19 charon kernel: fr_check_wrapper: m_len 0 fixed
 
 No panics or other messages. Everything is running fine now.
 
 Thanks again
 Joerg
 
 - -- 
 The beginning is the most important part of the work.
  				-Plato
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.18 (FreeBSD)
 
 iD8DBQFPzf5zSPOsGF+KA+MRAvC3AJsFAEf8axpmvfu3VPUiaFprhIT6KwCfSKMI
 J1Ywq6NYvDeHHXiVjuWSRWw=
 =k6q6
 -----END PGP SIGNATURE-----