From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Opportunistic GC Date: Mon, 08 Mar 2021 16:18:45 +0000 Message-ID: References: Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22604"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Pip Cet , Stefan Monnier , Eli Zaretskii , Emacs developers To: Philipp Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 08 17:22:55 2021 Return-path: Envelope-to: ged-emacs-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 1lJIel-0005ob-QY for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Mar 2021 17:22:55 +0100 Original-Received: from localhost ([::1]:59944 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lJIek-0006JI-Sj for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Mar 2021 11:22:54 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36314) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lJIaq-0003Pg-6P for emacs-devel@gnu.org; Mon, 08 Mar 2021 11:18:53 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:51622) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lJIam-0000SA-1R; Mon, 08 Mar 2021 11:18:51 -0500 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 128GIjxL022432 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Mon, 8 Mar 2021 16:18:45 GMT In-Reply-To: (Philipp Stephani's message of "Mon, 8 Mar 2021 17:14:51 +0100") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:266203 Archived-At: Philipp Stephani writes: [...] >> I also expect fork will work, I'm more wondering about interaction with >> sockets file descriptors or anything else in our codebase and/or in >> libraries we have loaded. >> >> I've read in the past this is an issue in practice in non trivial code >> and that, because the typical use of fork () nowadays is just to run >> afterward exec (), operating in the grey between the two was not really >> a good idea. But I don't have the reference now and if you say it works >> I've no reasons not to trust you. > > The restriction is that you can only call async-signal-safe functions > in subprocesses before exec. See e.g. the man page for fork on > GNU/Linux. Can we enforce that for our case? Andrea