Panic from ipfw_alloc_rule() after r334769 -> r334832

[David Wolfskill]

On Fri, Jun 08, 2018 at 11:40:37AM -0400, Jonathan T. Looney wrote:
> ...
> If anyone is hitting this bug and needs to get a working system in the
> meantime, you'll need to revert the following commits which implemented (or
> updated) this change:
> 
> r334830
> r334829
> r334824
> 
> Jonathan

I confirm that, having reverted the above (via:

    svn merge -c -334830 -c -334829 -c -334824 .

then rebuilding the kernel allowed the laptop to boot successfully.

(My laptop's kernel has IPFIREWALL wired in and explicitly does not have
IPFIREWALL_DEFAULT_TO_ACCEPT.)

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
Note that the presence of a pardon implies prior conviction for a crime.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20180608/34260030/attachment.sig>