From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) by sourceware.org (Postfix) with ESMTPS id A26243858C60 for ; Wed, 8 Dec 2021 14:06:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A26243858C60 Received: by mail-pj1-x1029.google.com with SMTP id gt5so2006142pjb.1 for ; Wed, 08 Dec 2021 06:06:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5LZeKEt7FwF+L0n4htFfSGLJZHGGRCpGcIEeGJNIQIY=; b=BPiYZVhmGTDVGM+PPVTN8nPCx+O9Xz7/zEFxNWIbdkPUnkwo2i7Z6iX2z0z02ZCSVw aXu9ghlzPonSjZXhFKYIQ0DVVk2c7kghXNbvtGVPVLJeTUiKp4MkX/+IKtlBk/rkkWL+ xtG/Ifp0Qw/SE4ntIzm0gUfBURetLLU6j3fHzL/z9bTE5ejONdAAmTuB4SogpLfZElyB /ALL41wypA2p58t837duK7EbuVnoQHvl3x35pm3qrclL4sn5wUYdAMdZcpsa86ZZ8Mq4 XQC5OHoBqKhXzzCQj83562+9KA9elyXJtAw+AqYaA7IuYK4j0TXi1Bb3zBXbBRNJAg9e fIxA== X-Gm-Message-State: AOAM532yhSzRcR7vputfy20wwifSYq1Ok0pNKS9PbsXM4kDBqW4moxLZ mI1LEc2YSoioGSKvFYs7B9SUgaJV2UZ75WBTYrg= X-Google-Smtp-Source: ABdhPJzpLPnapPJAyUNs6QgU+mEPYEppuz4eCcOwVdg1tdv6DdLJm0wgH2Is2Zplz9l+LIK3Zi88UsFaGnVB7xCP2M0= X-Received: by 2002:a17:902:904b:b0:143:73ff:eb7d with SMTP id w11-20020a170902904b00b0014373ffeb7dmr58286368plz.85.1638972409557; Wed, 08 Dec 2021 06:06:49 -0800 (PST) MIME-Version: 1.0 References: <87h7bjmnt0.fsf@oldenburg.str.redhat.com> <87czm7qv2f.fsf@igel.home> <875yrzmmw6.fsf@oldenburg.str.redhat.com> <878rwvqtyc.fsf@igel.home> <87sfv3l7ag.fsf@oldenburg.str.redhat.com> In-Reply-To: <87sfv3l7ag.fsf@oldenburg.str.redhat.com> From: "H.J. Lu" Date: Wed, 8 Dec 2021 06:06:13 -0800 Message-ID: Subject: Re: [PATCH] Fix glibc 2.34 ABI omission (missing GLIBC_2.34 in dynamic loader) To: Florian Weimer Cc: Andreas Schwab , Florian Weimer via Libc-alpha Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3022.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, URIBL_BLACK autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org 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: , X-List-Received-Date: Wed, 08 Dec 2021 14:06:56 -0000 On Wed, Dec 8, 2021 at 2:29 AM Florian Weimer via Libc-alpha wrote: > > * Andreas Schwab: > > > On Dez 08 2021, Florian Weimer wrote: > > > >> * Andreas Schwab: > >> > >>> On Dez 08 2021, Florian Weimer via Libc-alpha wrote: > >>> > >>>> The glibc 2.34 release really should have added a GLIBC_2.34 > >>>> symbol to the dynamic loader. > >>> > >>> Well, the ship has sailed. > >> > >> Has it? It's just software, we can change it. > > > > ABI is not software, it's a contract. > > But sometimes we have to to fix bugs. Again, what I propose is quite > different from a simple symbol change because distributions and users > can fix this now, well before the symbol is going to be used. I think we should do it and ask distributions to backport the patch. > I have considered using a stub DSO and mention that instead of libc.so.6 > in the libc.so linker script. But I'm not sure how we can prevent users > from linking against the moved symbol by bypassing the linker script. > That would produce ABI-incompatible binaries. We could turn it into a > compat symbol, but as long as it's in the dynamic symbol table, some > people will use it. > > Thanks, > Florian > -- H.J.