Panic from ipfw_alloc_rule() after r334769 -> r334832

[Jonathan T. Looney]

On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill <david at catwhisker.org>
wrote:
>
> Sorry for lack of much analysis; am at BSDCan.  jtl@ suggested that a
> sequence of changes involving memory allocation and ipfw counters is
> likely to be at issue.

Just to be clear, I speculated that this seemed like it could be caused by
r334824.

And, screen_1.jpg does indeed seem to point at that commit.

Jonathan