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 9C3AA385829F for ; Tue, 12 Jul 2022 13:17:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9C3AA385829F 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-615-9JqjrOWqMUu_U6ui6HbSSw-1; Tue, 12 Jul 2022 09:17:06 -0400 X-MC-Unique: 9JqjrOWqMUu_U6ui6HbSSw-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 81B2D801231; Tue, 12 Jul 2022 13:17:05 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.160]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 099D1141510F; Tue, 12 Jul 2022 13:17:03 +0000 (UTC) From: Florian Weimer To: Michael Matz via Libc-alpha Cc: Adhemerval Zanella Netto , Michael Matz , Alan Modra , caiyinyu , liuzhensong , WANG Xuerui , binutils@sourceware.org Subject: Re: glibc 2.36 - Slushy freeze (3 weeks to release) References: <7aba5486-ac02-2088-221e-513a6892817a@linaro.org> <612c015a-8d77-d0ee-773a-c51e9cb1d239@linaro.org> <74d08933-d426-c25d-8496-5bd1c76c396b@linaro.org> Date: Tue, 12 Jul 2022 15:17:02 +0200 In-Reply-To: (Michael Matz via Libc-alpha's message of "Tue, 12 Jul 2022 12:15:24 +0000 (UTC)") Message-ID: <87fsj6sc6p.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.85 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2022 13:17:10 -0000 * Michael Matz via Libc-alpha: > Hey, > > On Tue, 12 Jul 2022, Adhemerval Zanella Netto via Binutils wrote: > >> * Fix the R_LARCH_NONE generation and backport it to 2.38, or bump >> the minimum required version to 2.39. This will hold any inclusion >> on glibc until binutils is fixed. >>=20 >> * Add R_LARCH_NONE handling in boostraping. This is a simpler solution >> and although it might hinder some possible bugs in static linker, >> I think for current port status it the best option. > > Postel's law is always good advise. "Be strict in what you generate, be= =20 > lenient in what you accept", even more so for something so basic as a=20 > program loader. It seems ill-advised to use ld.so to force something=20 > onto users that can only be called a strive for purity. The problem here is that R_*_NONE has historically been used in binutils to indicate, =E2=80=9CI did not recognize the relocation in the input file= =E2=80=9D, while still generating an output file. And missing run-time relocations can be quite challenging to diagnose. In a sense, the loader has to reject R_*_NONE relocations to avoid generating bogus relocated data. Thanks, Florian