From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fweimer@redhat.com>
Received: from us-smtp-delivery-1.mimecast.com
 (us-smtp-delivery-1.mimecast.com [207.211.31.120])
 by sourceware.org (Postfix) with ESMTP id DE43C3857007
 for <libc-alpha@sourceware.org>; Wed,  1 Jul 2020 07:56:06 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DE43C3857007
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-461-r_Fkx-X6NP2RD3Zqd_ba8Q-1; Wed, 01 Jul 2020 03:56:04 -0400
X-MC-Unique: r_Fkx-X6NP2RD3Zqd_ba8Q-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com
 [10.5.11.14])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A340E10CE784;
 Wed,  1 Jul 2020 07:56:03 +0000 (UTC)
Received: from oldenburg2.str.redhat.com (ovpn-112-64.ams2.redhat.com
 [10.36.112.64])
 by smtp.corp.redhat.com (Postfix) with ESMTPS id D182A7610C;
 Wed,  1 Jul 2020 07:56:02 +0000 (UTC)
From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Why does pthread_mutex_destroy check for an in-use mutex?
References: <87lfk3lpx5.fsf@oldenburg2.str.redhat.com>
 <87y2o3d721.fsf@igel.home>
Date: Wed, 01 Jul 2020 09:56:01 +0200
In-Reply-To: <87y2o3d721.fsf@igel.home> (Andreas Schwab's message of "Wed, 01
 Jul 2020 09:32:22 +0200")
Message-ID: <878sg3llda.fsf@oldenburg2.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE,
 RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: libc-alpha@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Libc-alpha mailing list <libc-alpha.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/libc-alpha>,
 <mailto:libc-alpha-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/libc-alpha>,
 <mailto:libc-alpha-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jul 2020 07:56:08 -0000

* Andreas Schwab:

> On Jul 01 2020, Florian Weimer via Libc-alpha wrote:
>
>> This check does not seem to be mandated by POSIX.  As far as I can see,
>> it is the only place where __nusers is actually used.
>
> Is __nusers actually updated in the elision path?

It's not.  That would be a bug if it actually mattered, right?

Thanks,
Florian