From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS17314 8.43.84.0/22 X-Spam-Status: No, score=-4.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id F04DA1F8C6 for ; Wed, 4 Aug 2021 18:43:50 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id E04783953CFA for ; Wed, 4 Aug 2021 18:43:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E04783953CFA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1628102629; bh=H59Rl/vaenefEsKZITBwyEe7g50FEzSIod6iPj50LVw=; h=In-Reply-To:References:Date:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=qiMIJuHhpIbjGcDs49f9eOhdPd3PQtAaaNVXlBFpezTZv6kJfljyh2zm26rXtf/A4 PtmX07hNvhEw036+V7rgB+n5uRFB5W+QvHDfC1A9GB8fg9oKXaw1jzzJZzbKtuTUfL gzAedLnagj3whZ2Y2fJRiYWQXkVIstSAUK6mj3ls= Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by sourceware.org (Postfix) with ESMTPS id C7260386482B for ; Wed, 4 Aug 2021 18:43:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C7260386482B Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id 25667580B74 for ; Wed, 4 Aug 2021 14:43:28 -0400 (EDT) Received: from imap3 ([10.202.2.53]) by compute1.internal (MEProxy); Wed, 04 Aug 2021 14:43:28 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrieejgddutdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerreejnecuhfhrohhmpedfkggrtghkucghvghinhgsvghrghdfuceoiigrtghkseho fihlfhholhhiohdrohhrgheqnecuggftrfgrthhtvghrnhepueevueekkeekffeuudeiff egheeuleeukeffffehhfeghfegvdejleetgeevfeeunecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepiigrtghksehofihlfhholhhiohdrohhrgh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6F62B4200C3; Wed, 4 Aug 2021 14:43:27 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-548-g3a0b1fef7b-fm-20210802.001-g3a0b1fef Mime-Version: 1.0 Message-Id: <32c64940-8a1e-4cc5-870a-e00684cf8e29@www.fastmail.com> In-Reply-To: <87zgtxuxa8.fsf@igel.home> References: <87zgtxuxa8.fsf@igel.home> Date: Wed, 04 Aug 2021 14:43:06 -0400 To: "Florian Weimer" Subject: Re: Async cacellation and pthread_cleanup_push Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Zack Weinberg via Libc-alpha Reply-To: Zack Weinberg Errors-To: libc-alpha-bounces+e=80x24.org@sourceware.org Sender: "Libc-alpha" On Wed, Aug 4, 2021, at 9:58 AM, Andreas Schwab wrote: > Is pthread_cleanup_push supposed to work together with async > cancellation? Do you mean, is it supported for a sync cancellation to be enabled at th= e point of a call to pthread_cleanup_push? I am pretty sure that isn=E2=80= =99t required to work and I would expect it to have race windows that ar= e difficult to close. zw