From: Joseph Myers <joseph@codesourcery.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: <libc-alpha@sourceware.org>, Paul Eggert <eggert@cs.ucla.edu>,
Carlos O'Donell <carlos@redhat.com>, <libc-help@sourceware.org>
Subject: Re: Question regarding minimal supported Linux kernel headers (now it is 3.2.0)
Date: Tue, 12 Nov 2019 14:13:34 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1911121403360.30723@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20191112133953.0c3594ed@jawa>
On Tue, 12 Nov 2019, Lukasz Majewski wrote:
> The pselect6 conversion has been postponed on purpose as microblaze
> port gained support for pselect6 from Linux kernel 3.15. Between 3.2
> (minimal supported glibc Linux headers) and 3.15 this syscall is
> emulated and hence the generic code is convoluted.
>
> For the above reason the conversion of pselect6 has been postponed until
> the minimal glibc's Linux headers are bumped to the version after 3.15.
>
> Dear community - when the minimal glibc version may be increased?
>
> Are there any guidelines when the minimal version shall be increased
> (like once per X glibc releases) ?
Typically we increase the minimum kernel version used at runtime (which is
generally the same as the minimum kernel headers version), to the oldest
currently supported LTS Linux kernel version as listed at
<https://www.kernel.org/category/releases.html>, when this allows some
significant cleanup in glibc.
I think the next increase that is likely to allow significant cleanup is
moving to 4.4 as minimum kernel version (once 3.16 is EOL); 3.16 doesn't
allow much cleanup, but 4.4 allows removing most of the socketcall support
from glibc as all architectures have most of the separate socket syscalls
in 4.4 (a few were only added later for 32-bit SPARC in the compat syscall
table on 64-bit kernels).
I was *also* hoping that, before the next increase to the minimum kernel
version, we would have the changes Carlos proposed to remove the error on
startup for a too-old kernel, so that new glibc running under an old
kernel would only fail on actually trying to use one of the newer
syscalls, which might be rare on x86_64, and might not occur in the case
of container hosting systems that have backported newer syscalls to their
older kernel.
For pselect6, I suggest a preparatory change increasing the minimum
version for microblaze only and removing the racy emulation code from
glibc citing bug 9813, which could then be marked as FIXED with
appropriate milestone set once the emulation code has been completely
removed. (misc/pselect.c would change to an ENOSYS stub complete with
stub_warning call.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-11-12 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 12:39 Question regarding minimal supported Linux kernel headers (now it is 3.2.0) Lukasz Majewski
2019-11-12 14:13 ` Joseph Myers [this message]
2019-11-12 15:26 ` Adhemerval Zanella
2019-11-12 17:31 ` Joseph Myers
2019-11-12 18:13 ` Adhemerval Zanella
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1911121403360.30723@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=libc-help@sourceware.org \
--cc=lukma@denx.de \
/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).