From owner-freebsd-stable@freebsd.org Thu May 17 00:02:49 2018 Return-Path: Delivered-To: freebsd-stable@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 B60B3EDF2AC for ; Thu, 17 May 2018 00:02:49 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D2C948521A; Thu, 17 May 2018 00:02:48 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from [10.0.5.3] (noddy.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPSA id w4H01dcV078707 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 17 May 2018 10:01:41 +1000 (AEST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) X-Authentication-Warning: b3.hs: Host noddy.hs [10.0.5.3] claimed to be [10.0.5.3] Subject: Re: uptime / w coredumping on RELENG11 (i386 only) To: Dimitry Andric , Mike Tancsa Cc: FreeBSD-STABLE Mailing List References: <990862af-7bee-0d4b-c01f-d7fc8e5b6cfe@sentex.net> <955d6681-0048-5e09-cca6-4691b05bf48f@sentex.net> <18E4C626-410B-417F-89F2-4F16074749A1@FreeBSD.org> <865dd1e1-b29e-7d5b-41a5-e23a07b2f981@sentex.net> From: Dewayne Geraghty Message-ID: <9d2e0a4d-b2d7-315a-cc17-7965913aea39@heuristicsystems.com.au> Date: Thu, 17 May 2018 10:01:39 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Content-Language: en-AU X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 00:02:49 -0000 On 17/05/2018 7:17 AM, Dimitry Andric wrote: > On 16 May 2018, at 15:54, Mike Tancsa wrote: >> On 5/15/2018 2:31 PM, Dimitry Andric wrote: >>> On 15 May 2018, at 20:22, Mike Tancsa wrote: >>>>> Anyone else see this ? >>> See . There is a fix coming up. >> I tried the patch and did a full rebuild and it indeed fixed the problem >> for me. Is the bug potentially more wide spread that just libxo ? Also >> does it possibly affect amd64, just in a non obvious way ? > Yes to both, at least theoretically. The problem is actually in > elftoolchain's strip command, which can mess up the TLS section in an > executable or shared library. When the dynamic linker loads such a bad > file, it will setup incorrect TLS data, which can lead to crashes. > > In case of libxo.so.0, this appears to have been caused by clang 6 > giving a slightly different ELF layout than clang 5. During buildworld, > libxo.so.0 is built with debugging information, which is later copied > to a libxo.so.0.debug file, while it is removed from the original > libxo.so.0 file. > > Up to this point, everything is still fine with libxo.so.0, still, but > during installworld, the file is stripped *again*, by install -s (this > is something we should revisit because it seems no longer useful). This > second round of stripping messes up the TLS section. > > -Dimitry > Revisit? Perhaps, but it seems that its a regression against clang6 over clang5.  Looking at https://svnweb.freebsd.org/base?view=revision&revision=333600 its appears that the section flags are correctly applied now.  When 333600 enters 11.1Beta?, do you think the build/installation process requires revision? Its a little disappointing to hear that the stripping process breaks the output, if applied >1. -- Influence national support against IP address spoofing (pretending to be someone else), refer: http://www.bcp38.info/index.php/Main_Page