From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31770 invoked from network); 5 Apr 2023 12:13:37 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 5 Apr 2023 12:13:37 -0000 Received: (qmail 3707 invoked by uid 550); 5 Apr 2023 12:13:34 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 3682 invoked from network); 5 Apr 2023 12:13:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680696802; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=b237PXRbDid/epfYwBA9ahb4fsQUYWNyOIokAn2vzMg=; b=QCflyg/TsaJGzU5hXneEn9EwAK5zYpQ18BTEd72v8qLunQzhHqSzBVs44WyJWu7qbCzHW4 LkOcUksxyeLPF0PIcx2sLeNp2YmMcG17C0CXFmH79tM8l+VlTFn8EozqE9G3jMLRPWzbdd jmyc6xfod40gTKpZRDduY0cZa72zCGI= X-MC-Unique: MRbl2GVgNpO8_sJJVpcKvA-1 From: Florian Weimer To: Rich Felker Cc: musl@lists.openwall.com References: <20230405115445.GG3298@brightrain.aerifal.cx> Date: Wed, 05 Apr 2023 14:13:16 +0200 In-Reply-To: <20230405115445.GG3298@brightrain.aerifal.cx> (Rich Felker's message of "Wed, 5 Apr 2023 07:54:46 -0400") Message-ID: <874jpule77.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: [musl] Re: [PATCH v9 0/13] implement dlmem() function (fwd) * Rich Felker: > Well this is disturbing. We probably need to fix gcc here (and a lot > of code in the wild may be broken) because musl has no such locking > where it doesn't belong. We have a helper function in glibc (_dl_find_object) that replaces all the previous object traversal logic and caching in libgcc, so it's no longer an issue with current gcc and glibc. Unfortunately that means that the generic dl_iterate_phdr code will be fixed by adding its own locking. Thanks, Florian