From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id F2B7B3AC2FDF for ; Fri, 7 Jul 2023 11:10:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org F2B7B3AC2FDF Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1688728231; 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=yGiyyaleV1AQ64KkWcqj/bpFQstbr64zMUPu+I75OsM=; b=N6b5frsiabxO5B86eWaebJOKOTFW9u5pDFyu6YdLmaXUD4MawRLWS88noOJmleGhrz7ixF by2er6UYzdLiyz6KW4OLN96ks0SWYN6/oBtFrEhuBfbau0zpuO8ffN+epKIoF6n5oMMGjx 7alxeXX5As4roEbei6cP8PEonGe5r9s= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-221-MoO6CavZPFmZjcMeF0s8Mw-1; Fri, 07 Jul 2023 07:10:30 -0400 X-MC-Unique: MoO6CavZPFmZjcMeF0s8Mw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 240741064AF8; Fri, 7 Jul 2023 11:10:30 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.31]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CF5F41454151; Fri, 7 Jul 2023 11:10:28 +0000 (UTC) From: Florian Weimer To: Adhemerval Zanella Netto Cc: Carlos O'Donell , Maxim Kuvyrkov , libc-alpha@sourceware.org Subject: Re: [PATCH 00/33] RFC: RELRO link maps References: <874jmjwid9.fsf@oldenburg.str.redhat.com> <741d667e-818e-1552-a496-7d6bb1212313@redhat.com> <87edlmfj17.fsf@oldenburg.str.redhat.com> Date: Fri, 07 Jul 2023 13:10:26 +0200 In-Reply-To: (Adhemerval Zanella Netto's message of "Wed, 5 Jul 2023 14:58:40 -0300") Message-ID: <873520geot.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.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.6 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_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * Adhemerval Zanella Netto: > On 05/07/23 14:48, Carlos O'Donell wrote: >> On 7/5/23 11:57, Florian Weimer wrote: >>> * Carlos O'Donell: >>> >>>> On 7/4/23 16:07, Florian Weimer via Libc-alpha wrote: >>>>> I forgot to mention that I tested this on aarch64-linux-gnu, >>>>> i686-linux-gnu, powerpc64le-linux-gnu (with the hash MMU and protection >>>>> keys on POWER8, and with the radix MMU on POWER10, so without protection >>>>> keys), and x86-64-linux-gnu. Force-enabling protection keys on x86-64 >>>>> causes malloc/tst-mallocfork* tests to fail because we cannot read >>>>> dynamic linker data structures anymore during lazy binding. >>>> >>>> Fails pre-commit CI for 32-bit ARM: >>>> https://patchwork.sourceware.org/project/glibc/patch/477cc628fed2769f25399d7674080dd257a80d46.1688499219.git.fweimer@redhat.com/ >>>> >>>> === glibc tests === >>>> >>>> Running glibc:dlfcn ... >>>> FAIL: dlfcn/tststatic4 >>>> >>>> === Results Summary === >>> >>> Yes, already saw that report. Any idea why? I don't have an easy way >>> to reproduce failures on that architecture, unfortunately. >> >> I don't know why. >> >> Maxim and I have discussed what to do in these scenarios and what expectations the >> community should have about the pre-commit CI test owner. >> >> My understanding is that Linaro is here to help determine why the failure occurred >> and work with you to find a solution. >> >> Notes: >> https://sourceware.org/glibc/wiki/PreCommitCI > > I will take a look of what might be happening here. I can't find the failure anymore. What's the target triplet for this builder? What's the closest build-many-glibcs.py configuration? Thanks, Florian