Date: Mon, 25 Jun 2018 14:46:33 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Mark Johnston <markj@freebsd.org> Cc: Steven Hartland <steven.hartland@multiplay.co.uk>, Alan Cox <alc@rice.edu>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r335171 - head/sys/vm Message-ID: <20180625114633.GE2430@kib.kiev.ua> In-Reply-To: <20180625103020.GF1232@pesky> References: <201806141941.w5EJf2qa069373@repo.freebsd.org> <c241bd08-eb94-152e-c1f1-d77dc6987908@multiplay.co.uk> <F220E356-D55E-48B9-9AF0-ABBF41A74FC7@rice.edu> <603230da-cfe2-e3e2-bd9a-f5230b30e371@multiplay.co.uk> <20180615110303.GN2493@kib.kiev.ua> <20180625103020.GF1232@pesky>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 25, 2018 at 06:30:20AM -0400, Mark Johnston wrote: > On Fri, Jun 15, 2018 at 02:03:03PM +0300, Konstantin Belousov wrote: > > On Fri, Jun 15, 2018 at 11:03:06AM +0100, Steven Hartland wrote: > > > On 15/06/2018 00:07, Alan Cox wrote: > > > > > > > >> On Jun 14, 2018, at 5:54 PM, Steven Hartland > > > >> <steven.hartland@multiplay.co.uk > > > >> <mailto:steven.hartland@multiplay.co.uk>> wrote: > > > >> > > > >> Out of interest, how would this exhibit itself? > > > >> > > > > > > > > A panic in vm_page_insert_after(). > > > > > > > So just to confirm this couldn't cause random memory corruption of the > > > parent process? > > > > No, or to put it more sincere, I highly doubt it. > > > > Also, I do not think that this Go issue will be solved serendipitously > > by some FreeBSD bug fix. So far it is indicative that either the > > situation is too unique for the Go runtime so it is not exposed by other > > programs (which is quite doubtful), or this is a bug in Go runtime. > > > > The only way forward is to understand what exactly is broken for the > > situation. This requires at least deep knowledge the Go garbage collector > > internal working, which itself supposes understanding of the Go runtime > > and Go environment. I do not mean explanation of the assert, but the > > root cause that eventually triggers the assert. They are somewhat > > disjoint in time, I believe. > > Is this problem summarized anywhere? In particular, is there a > reasonably minimal test case that reproduces the problem? Go bug report has the reproducer. I do not remember if this is the same snippet that I used. https://github.com/golang/go/issues/15658 When I looked at it, it took tens of minutes to trigger on sandy bridge machine. Note that recent reporters indicate that they need to run the test for a whole day. It might be that there are more then one issues, and some of them are fixed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180625114633.GE2430>