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.2 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,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 426851F8C6 for ; Wed, 4 Aug 2021 15:36:00 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 2E3593948829 for ; Wed, 4 Aug 2021 15:35:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E3593948829 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1628091359; bh=hwfw6FhVNSdTUdWieb88ssEJnqCFcRPQ9tyNPOiS23I=; h=To:Subject:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=CSwU46jVKpsbdzGGtI0SMLG2qzXgkHgEKTtLs/LfQwv6mWxPZAIWpUTvdlzcLNCMU 7ZW1RIst0NzXXHMy3WMBDDf7CAQNwlT9J2pliGQunTiwRjd1nLTy6hI/tRG3LldL10 aHd8eg27SuF/XQxCJ8xesRIZP3KsiJnx2Rg3wIn4= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTP id 67CE83948829 for ; Wed, 4 Aug 2021 15:33:37 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 67CE83948829 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-236-_Hci4_L2PzWdiZ-N6VDJaw-1; Wed, 04 Aug 2021 11:33:35 -0400 X-MC-Unique: _Hci4_L2PzWdiZ-N6VDJaw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EEB9C94EE0; Wed, 4 Aug 2021 15:33:34 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.123]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 277891060040; Wed, 4 Aug 2021 15:33:33 +0000 (UTC) To: Andreas Schwab Subject: Re: Async cacellation and pthread_cleanup_push References: <87zgtxuxa8.fsf@igel.home> Date: Wed, 04 Aug 2021 17:33:32 +0200 In-Reply-To: <87zgtxuxa8.fsf@igel.home> (Andreas Schwab's message of "Wed, 04 Aug 2021 15:58:23 +0200") Message-ID: <87fsvp9qcz.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain 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: Florian Weimer via Libc-alpha Reply-To: Florian Weimer Cc: libc-alpha@sourceware.org Errors-To: libc-alpha-bounces+e=80x24.org@sourceware.org Sender: "Libc-alpha" * Andreas Schwab: > Is pthread_cleanup_push supposed to work together with async > cancellation? In our implementation? I think so. POSIX doesn't require it, though. Thanks, Florian