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=-2.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RDNS_DYNAMIC,SPF_HELO_PASS,SPF_PASS,URIBL_BLACK shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.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 203D51F5AE for ; Tue, 4 May 2021 12:04:40 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 1194C398205D; Tue, 4 May 2021 12:04:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1194C398205D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1620129879; bh=1r6Xs0M+SzJ4eaZnXy4smnwHM3e8YseGo+38e9nsAd8=; 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=w/6HHMpaxcJxX6iOnimkWwcZ4vfb9yFuARBYVxi4ES+CByxlT+QhqlWFR7pnadUym Ueu0ZES6GQmJguT0zkAzo49msRIfr3di3/gBCicO7ZO4Gd1jSD4rCtCQmRCmdmqmku ADLn3Syy41kChEV1iNsaXMB/sOwo66D9UXDJirCM= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id E06503857033 for ; Tue, 4 May 2021 12:04:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E06503857033 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-487-ShOvjC8wMQmVJyqnEkZBIg-1; Tue, 04 May 2021 08:04:31 -0400 X-MC-Unique: ShOvjC8wMQmVJyqnEkZBIg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id AC4E9DF8A9; Tue, 4 May 2021 12:04:30 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-112-137.ams2.redhat.com [10.36.112.137]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 949DC60C0F; Tue, 4 May 2021 12:04:29 +0000 (UTC) To: "H.J. Lu" Subject: Re: [RFC] elf: Implement filtering of symbols historically defined in libpthread References: <87h7jqguew.fsf@oldenburg.str.redhat.com> Date: Tue, 04 May 2021 14:04:43 +0200 In-Reply-To: (H. J. Lu's message of "Tue, 4 May 2021 04:47:38 -0700") Message-ID: <87k0oeln6s.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.79 on 10.5.11.12 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: Andreas Schwab , GNU C Library Errors-To: libc-alpha-bounces@sourceware.org Sender: "Libc-alpha" * H. J. Lu: > Since we want to detect the binaries which were linked against glibc > older than 2.34, we should use the glibc version to check the old > binaries. The patch attempts to detect old main programs by looking for the GLIBC_2.34 symbol version. Since we added __libc_start_main@GLIBC_2.34 (which is called from our version of _start), all standard main programs linked with glibc 2.34 or later will have this symbol version. > Of course, we should make a complete list of functions which are > really implemented in libpthread.so and will be moved to libc.so in > glibc 2.34. I'm not sure if it is necessary to do this for *all* symbols. Formally, a symbol added after glibc 2.0 is not suitable for detecting the potential multi-threaded nature of a process because the application could be built for an earlier glibc version, where the symbol is not available, but pthread_create can still create new threads. The use of pthread_mutexattr_gettype@@GLIBC_2.1 as the detection symbol does not follow the rule, of course. With the explicit table approach (as in the patch), we can add additional lookup symbols later, so I think we can start out with the GLIBC_2.0 and GLIBC_2.1 symbols plus thrd_exit (the latter is also used by gnulib for some reason). Thanks, Florian