From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fw@deneb.enyo.de>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: "Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: Update syscall lists for Linux 5.12
Date: Sun, 2 May 2021 16:19:09 -0400 [thread overview]
Message-ID: <15c019d5-036f-91cb-0926-25703425c364@redhat.com> (raw)
In-Reply-To: <878s4wzzvi.fsf@mid.deneb.enyo.de>
On 5/2/21 3:42 PM, Florian Weimer wrote:
> * Carlos O'Donell via Libc-alpha:
>
>> On 4/27/21 8:07 PM, Dmitry V. Levin wrote:
>>> On Tue, Apr 27, 2021 at 11:52:27PM +0000, Joseph Myers wrote:
>>>> Linux 5.12 has one new syscall, mount_setattr. Update
>>>> syscall-names.list and regenerate the arch-syscall.h headers with
>>>> build-many-glibcs.py update-syscalls.
>>>
>>> Yes, this looks correct, mount_setattr syscall was introduced
>>> by Linux kernel commit v5.12-rc1~64^2~6.
>>>
>>>
>>
>> And a few more were added...
>>
>> error: kernel syscall 'quotactl_path' (443) not known to glibc
>> error: kernel syscall 'landlock_create_ruleset' (444) not known to glibc
>> error: kernel syscall 'landlock_restrict_self' (446) not known to glibc
>> error: kernel syscall 'landlock_add_rule' (445) not known to glibc
>> info: glibc tables are based on kernel version 5.12
>> info: installed kernel headers are version 5.12
>
> It looks like you are using a development kernel that hasn't changed
> its version to 5.13 yet.
It's upstream Linus tree, but I thought I'd pinned it to 5.12... and you
are right it looks like they haven't updated the top-level Makefile:VERSION
yet even though they've started merging in changes for 5.13.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-05-02 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 23:52 Joseph Myers
2021-04-28 0:07 ` Dmitry V. Levin
2021-05-02 19:17 ` Carlos O'Donell
2021-05-02 19:42 ` Florian Weimer
2021-05-02 20:19 ` Carlos O'Donell [this message]
2021-05-02 21:11 ` Andreas Schwab
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=15c019d5-036f-91cb-0926-25703425c364@redhat.com \
--to=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
/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).