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 1CFDA3858432 for ; Fri, 30 Jul 2021 06:58:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1CFDA3858432 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-502-YG8LO3jvMSSrno_Rd5wBJg-1; Fri, 30 Jul 2021 02:58:18 -0400 X-MC-Unique: YG8LO3jvMSSrno_Rd5wBJg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 99BF6800D55; Fri, 30 Jul 2021 06:58:17 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.123]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C1B335F707; Fri, 30 Jul 2021 06:58:16 +0000 (UTC) From: Florian Weimer To: xiechengliang via Libc-help Cc: xiechengliang Subject: Re: Glibc 2.31 and kernel 5.10 compatibility consultation References: <483841a75317424ea2c31189190afc7d@huawei.com> Date: Fri, 30 Jul 2021 08:58:14 +0200 In-Reply-To: <483841a75317424ea2c31189190afc7d@huawei.com> (xiechengliang via Libc-help's message of "Fri, 30 Jul 2021 04:03:38 +0000") Message-ID: <87tukcz3sp.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.79 on 10.5.11.16 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.9 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-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2021 06:58:21 -0000 * xiechengliang via Libc-help: > Through the RELEASE of glibc 2.31, it is found that the highest kernel > version used in the test is 5.4, Is there a compatibility problem if > the kernel uses 5.10? No, on the main architectures, all recent glibc releases are compatible with all kernels from Linux 3.2 at run time. There might be some quirks around building glibc itself due to header incompatibilities, but those do not extend to run-time issues. Thanks, Florian