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
weird, my grep-fu failed me hardcore i guess.
Will fix shortly.
On Fri, Jun 8, 2018 at 5:40 PM, Jonathan T. Looney wrote:
> On Fri, Jun 8, 2018 at 10:52 AM, Jonathan T. Looney
> wrote:
> >
> > On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill
> wrote:
> > >
> > > Sorry for lack of much
On Fri, Jun 8, 2018 at 10:52 AM, Jonathan T. Looney wrote:
>
> On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill
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.
On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill
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
