From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward102p.mail.yandex.net (forward102p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:102]) by sourceware.org (Postfix) with ESMTPS id 293A63858432 for ; Fri, 30 Jul 2021 06:59:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 293A63858432 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=yandex.ru Received: from iva5-c4e83e876e06.qloud-c.yandex.net (iva5-c4e83e876e06.qloud-c.yandex.net [IPv6:2a02:6b8:c0c:9324:0:640:c4e8:3e87]) by forward102p.mail.yandex.net (Yandex) with ESMTP id 157FC54C1BD0; Fri, 30 Jul 2021 09:59:12 +0300 (MSK) Received: from iva6-2d18925256a6.qloud-c.yandex.net (iva6-2d18925256a6.qloud-c.yandex.net [2a02:6b8:c0c:7594:0:640:2d18:9252]) by iva5-c4e83e876e06.qloud-c.yandex.net (mxback/Yandex) with ESMTP id d9X40WC28E-xBIejQx7; Fri, 30 Jul 2021 09:59:12 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1627628352; bh=eEuLkskt0lFy9K/BLPyQPMmfHsNIlICc50z+1ekWVko=; h=References:Date:To:From:Subject:Message-ID:In-Reply-To; b=HRxt+yZQX9ApLxJ5WGAQTAY20eEDstlULrnI/ITdwCHFxeudwo9scO48tcZa6uwMY S6q0DOLcJVyLvd1DTcQI/x+u2Prn7UpTdRKsCbjC1Uu1Xha23tBWXTzobYjxv01tAb 16RjPE0dZeO/pnEwaxHf7wWSOSxjJXq+g06x8uWY= Authentication-Results: iva5-c4e83e876e06.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by iva6-2d18925256a6.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id SGJcVtpExu-xBoqQYGH; Fri, 30 Jul 2021 09:59:11 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Message-ID: <8f824892d3ff2c22652e7af8be67c7ff495e4897.camel@yandex.ru> Subject: Re: Glibc 2.31 and kernel 5.10 compatibility consultation From: Konstantin Kharlamov To: xiechengliang , "libc-help@sourceware.org" Date: Fri, 30 Jul 2021 09:59:10 +0300 In-Reply-To: <483841a75317424ea2c31189190afc7d@huawei.com> References: <483841a75317424ea2c31189190afc7d@huawei.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, SPF_HELO_NONE, SPF_PASS, 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:59:16 -0000 Linux kernel motto is "we don't break userspace". So please don't worry, nothing is gonna happen with your apps if you make use of a newer kernel version. On Fri, 2021-07-30 at 04:03 +0000, xiechengliang via Libc-help wrote: > Hi all, > 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? > Through the changelog of the new version of glibc, it is found that the new > version has updated syscall lists for Linux 5.10,  In addition, are there any > other adaptation points for the 5.10 kernel? >    Has the community done a compatibility test between kernel 5.10 and glibc > 2.31? > > Thank you > Xie Chengliang > >