public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: xiechengliang via Libc-help <libc-help@sourceware.org>
Cc: xiechengliang <xiechengliang1@huawei.com>
Subject: Re: Glibc 2.31 and kernel 5.10 compatibility consultation
Date: Fri, 30 Jul 2021 08:58:14 +0200	[thread overview]
Message-ID: <87tukcz3sp.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <483841a75317424ea2c31189190afc7d@huawei.com> (xiechengliang via Libc-help's message of "Fri, 30 Jul 2021 04:03:38 +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


  reply	other threads:[~2021-07-30  6:58 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 [this message]
2021-07-30  6:59 ` Konstantin Kharlamov

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=87tukcz3sp.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --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).