From owner-freebsd-hackers@freebsd.org  Wed Feb 14 10:35:00 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34CB9F1504A
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Wed, 14 Feb 2018 10:35:00 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A35536FC60
 for <freebsd-hackers@freebsd.org>; Wed, 14 Feb 2018 10:34:59 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w1EAYqw8015340
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Wed, 14 Feb 2018 12:34:55 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w1EAYqw8015340
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id w1EAYpta015339;
 Wed, 14 Feb 2018 12:34:51 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
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>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16f4ce10-70d3-12f4-2246-e8ab44ba511f@multiplay.co.uk>
User-Agent: Mutt/1.9.3 (2018-01-21)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Feb 2018 10:35:00 -0000

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.