Date: Fri, 8 Jun 2018 10:52:08 -0400 From: "Jonathan T. Looney" <jtl@freebsd.org> To: David Wolfskill <david@catwhisker.org>, FreeBSD Current <current@freebsd.org> Subject: Re: Panic from ipfw_alloc_rule() after r334769 -> r334832 Message-ID: <CADrOrmuaVhk1nnxV74mj-%2BmhRmGUBcPE7Xw3h52=z7itvuAcMQ@mail.gmail.com> In-Reply-To: <20180608133836.GM1389@albert.catwhisker.org> References: <20180608133836.GM1389@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill <david@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADrOrmuaVhk1nnxV74mj-%2BmhRmGUBcPE7Xw3h52=z7itvuAcMQ>