Date: Wed, 14 Feb 2018 12:34:51 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: Stale memory during post fork cow pmap update Message-ID: <20180214103451.GF94212@kib.kiev.ua> In-Reply-To: <16f4ce10-70d3-12f4-2246-e8ab44ba511f@multiplay.co.uk> References: <5A7E7F2B.80900@dell.com> <20180210111848.GL33564@kib.kiev.ua> <5A7F6A7C.80607@dell.com> <20180210225608.GM33564@kib.kiev.ua> <5A82AB7C.6090404@dell.com> <20180213133010.GD94212@kib.kiev.ua> <aadcb842-fb07-e856-e525-2e562d5a9e2d@sentex.net> <16f4ce10-70d3-12f4-2246-e8ab44ba511f@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 14, 2018 at 09:06:18AM +0000, Steven Hartland wrote: > @kib do you think this issue could be the cause of the golang crashes > during fork that we spoke about a while back > https://github.com/golang/go/issues/15658 > > If its possible is there anything specific I could do to force a regular > occurrence in order to confirm or deny it? I have no idea. It is much easier to check then to try plotting theories about applicability. I will be not surprised by either outcome.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180214103451.GF94212>