On Thu, Jun 29, 2017 at 09:41:27AM -0700, Brad Fitzpatrick wrote:
> I only identified it as a kernel crash the other day. We had assumed it was
> our bug prior to that.
> But many similar looking bugs exist already:
Those are all completely different bugs; the only thing they have in
common is the kernel-level equivalent of SIGSEGV.
> > https://github.com/golang/go/
which leads to
which is fixed but the fix is apparently not in 7.1.
Also, tech-kern is the list for kernel issues. Adjusting accordingly.