From owner-svn-src-all@freebsd.org Mon Jun 25 10:30:25 2018 Return-Path: Delivered-To: svn-src-all@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 DF8BA1005DAF; Mon, 25 Jun 2018 10:30:24 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5587B75F11; Mon, 25 Jun 2018 10:30:24 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-ed1-x533.google.com with SMTP id q24-v6so3422257edr.1; Mon, 25 Jun 2018 03:30:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=vp1NsWE71vOk/lSTSqALtv3sf4qGSDylIZaP6Kk02Co=; b=UENmox5JOjn5FZzKOGbTJpD1sD7tSqVCyVBct22BM6MRiZ2Lm5pbQndboTscJmR3f6 E7eMtjojiIMjROBaP8Dia73mCLr5fjihE0kp+Ua8EPyg1L08EKoZin8vRonKCnyOu+iA ZiF3+Bwky3apB1f2gNAJQJ3+jQbD7KMWn9QxGmUql21+JTvG2oBtLgS5njDfqSs/exWB O01eaSVooVXWiixzyEKEBxC71vhDm3tNG8Aw3y+xPOzLo2SjSXUlxi7JV6XigQRd2w5S nhbwsp/SaPfSNwM3EFGVxonxaQr698FXVrPhssd+TV3ykGhbMoEG9ZAfp0ptvi/VdfiW sBmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=vp1NsWE71vOk/lSTSqALtv3sf4qGSDylIZaP6Kk02Co=; b=q+YVKBvAhXrwufl9TAtpfVCmKEhQ8JappJP1Zg0qWfWBYUq8W4ujuzfY9e0Qb1zjww PIYUHlBAAK7NBikaevh8/eaeLF8rbOuOSlDWFxxAh52QxNPHn48KsYMRLB4TL+YSOxvk lXUtg+bxHgYRRHwJFt9p49VUlz2FK+iFh4PprJ69jDE4AEfJ/NNn0i5U+hAQxrNqsOtZ oO1u+enZxHTYwwEvUHJpiiJNrnfDLfAOZSI/o/Aj+J5X3gX/fyPOUUcp3UpmYLQEQYKA oU5KBtE1PaPZSV0pdCEVxU8Q6qAPFBqNIiqdGU3XmgJa57FdTDWw3aDKhpU8fWb9JZEl Ggag== X-Gm-Message-State: APt69E1lj3mwzGxsHNwmn/3qnNkeksE+Oh1wEqwYxAQYTIZ/xmq/2fC2 WdkwSXvpoilZz6TTUTQ0MFc= X-Google-Smtp-Source: ADUXVKLMgPInIVNYW53Gs9f2C7giE/j8jZCx+tn/62zLeRt67MWib6wFOGtupTXM96t89TowBpEyvw== X-Received: by 2002:a50:d690:: with SMTP id r16-v6mr2230794edi.259.1529922622861; Mon, 25 Jun 2018 03:30:22 -0700 (PDT) Received: from pesky ([37.153.233.130]) by smtp.gmail.com with ESMTPSA id d11-v6sm6397207edh.61.2018.06.25.03.30.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Jun 2018 03:30:21 -0700 (PDT) Sender: Mark Johnston Date: Mon, 25 Jun 2018 06:30:20 -0400 From: Mark Johnston To: Konstantin Belousov Cc: Steven Hartland , Alan Cox , src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r335171 - head/sys/vm Message-ID: <20180625103020.GF1232@pesky> References: <201806141941.w5EJf2qa069373@repo.freebsd.org> <603230da-cfe2-e3e2-bd9a-f5230b30e371@multiplay.co.uk> <20180615110303.GN2493@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180615110303.GN2493@kib.kiev.ua> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 10:30:25 -0000 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 > > >> > >> > 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?