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.133.124]) by sourceware.org (Postfix) with ESMTP id B546A383B435 for ; Thu, 8 Jul 2021 06:25:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B546A383B435 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-114-Ty3n-MkMMvCPpO3qZBhz9g-1; Thu, 08 Jul 2021 02:25:51 -0400 X-MC-Unique: Ty3n-MkMMvCPpO3qZBhz9g-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0BB4C800C78; Thu, 8 Jul 2021 06:25:50 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-115-5.ams2.redhat.com [10.36.115.5]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 66425100EBAF; Thu, 8 Jul 2021 06:25:48 +0000 (UTC) From: Florian Weimer To: John Mellor-Crummey via Libc-alpha Cc: Adhemerval Zanella , John Mellor-Crummey , Xiaozhu Meng , Matt Legendre , "Mark W. Krentel" Subject: Re: [PATCH 0/5] Some rtld-audit fixes References: <20210707182610.3940620-1-adhemerval.zanella@linaro.org> <269adf45-f99a-6629-75ae-8a43bf906456@linaro.org> Date: Thu, 08 Jul 2021 08:25:46 +0200 In-Reply-To: (John Mellor-Crummey via Libc-alpha's message of "Wed, 7 Jul 2021 14:22:14 -0500") Message-ID: <87r1g9xqxh.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.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham 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: Thu, 08 Jul 2021 06:25:55 -0000 * John Mellor-Crummey via Libc-alpha: > Now I am a bit worried. Are your expecting the LD_AUDIT patches you > posted today to make it into 2.34 or will they be delayed until 2.35 > as well? Let me approach this differently. Why is the glibc 2.34 release important to you? To be honest, I expect whether the fixes land in glibc 2.34 or 2.35 has little impact on when the changes land in the hands of your users. So far, everything looks backportable. I'm aware of just one distribution with long-term support that plans to use glibc 2.34 (Red Hat Enterprise Linux 9), and given that there is a strong desire to have the changes in Red Hat Enterprise Linux 8, we'd have to backport them to Red Hat Enterprise Linux 9 if they aren't included in the glibc 2.34 release proper. (I'd consider a LAV_CURRENT bump backportable, too.) Thanks, Florian