From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: xiechengliang <xiechengliang1@huawei.com>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: Glibc 2.31 and kernel 5.10 compatibility consultation
Date: Fri, 30 Jul 2021 09:59:10 +0300 [thread overview]
Message-ID: <8f824892d3ff2c22652e7af8be67c7ff495e4897.camel@yandex.ru> (raw)
In-Reply-To: <483841a75317424ea2c31189190afc7d@huawei.com>
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
>
>
prev parent reply other threads:[~2021-07-30 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 4:03 xiechengliang
2021-07-30 6:58 ` Florian Weimer
2021-07-30 6:59 ` Konstantin Kharlamov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f824892d3ff2c22652e7af8be67c7ff495e4897.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=libc-help@sourceware.org \
--cc=xiechengliang1@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).