From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Newsgroups: gmane.lisp.guile.devel Subject: Re: bug#22608: Module system thread unsafety and .go compilation Date: Mon, 10 Oct 2022 10:07:56 +0200 Message-ID: <87v8os3xur.fsf@gnu.org> References: <8737t1k5yk.fsf@T420.taylan> <87d0w4ezst.fsf@gnu.org> <87lepr412m.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1297"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) Cc: 22608@debbugs.gnu.org, guile-devel@gnu.org To: Maxim Cournoyer Original-X-From: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Mon Oct 10 10:28:38 2022 Return-path: Envelope-to: guile-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oho9N-00007j-Vk for guile-devel@m.gmane-mx.org; Mon, 10 Oct 2022 10:28:37 +0200 Original-Received: from localhost ([::1]:54674 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oho9L-0006Od-GB for guile-devel@m.gmane-mx.org; Mon, 10 Oct 2022 04:28:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50400) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohnpQ-0003u1-S6 for guile-devel@gnu.org; Mon, 10 Oct 2022 04:08:00 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34230) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohnpQ-0007JI-Hu; Mon, 10 Oct 2022 04:08:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:In-Reply-To:Date:References:Subject:To: From; bh=7y+nZN4PbZkcWuUOtf5+CoEmsLPW9k1MmuLbLeAhGgE=; b=nZPi7nl/ZD8go4s8qTlN smYf8jz5rk6tOC9lm8dI9b5JDRRrlI9jCA9suoi6wmGwqDhf2jzbMZalSEIskoo01pAGk/ygsstLJ wAG5u66dzTOcEJQADK/JmiHRIZe2Y7qv94ALuRKWRCmOavB0ofv2Liups+E9m022RbVRokB4x/hPQ nUuibFjr7zh5ugvAIxsDmsuF1vO54l3851HJyl8S32uoKXXddOsR86oOpLlH/dA25pWfygmQvqQAo 3VUpsifQiCMwGsxbGEKr86HGlFF7MQm3sj4GDZ8nPm2XCZx6jvTQklRavLcooQE4b4wjWX1zr1Aoc GH51PbI9onGteg==; Original-Received: from [2001:660:6102:320:e120:2c8f:8909:cdfe] (port=43288 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ohnpP-0007pL-SW; Mon, 10 Oct 2022 04:08:00 -0400 X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: Nonidi 19 =?utf-8?Q?Vend=C3=A9miaire?= an 231 de la =?utf-8?Q?R=C3=A9volution=2C?= jour du Tournesol X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu In-Reply-To: <87lepr412m.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 07 Oct 2022 20:21:37 -0400") X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.io gmane.lisp.guile.devel:21394 Archived-At: Hi! Maxim Cournoyer skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: [...] >> For the record, these issues should be fixed in Guile 2.2.4: >> >> 533e3ff17 * Serialize accesses to submodule hash tables. >> 46bcbfa56 * Module import obarrays are accessed in a critical section. >> 761cf0fb8 * Make module autoloading thread-safe. >> >> =E2=80=98guix pull=E2=80=99 now defaults to 2.2.4, so we=E2=80=99ll see = if indeed those crashes >> disappear. > > I think we haven't seen these in the last 4 years! We still have > references to https://bugs.gnu.org/15602 in our code base though; > although the upstream issue appears to have been fixed. Could we remove > the workarounds now? The module thread-safety issue discussed here appears to be done. However the workarounds for must remain: that specific issue is still there. Thanks, Ludo=E2=80=99.