Bug 29499 - Check failed on misc/tst-glibcsyscalls while building for RISCV64 on a unmatched hardware
Summary: Check failed on misc/tst-glibcsyscalls while building for RISCV64 on a unmatc...
Status: RESOLVED FIXED
Alias: None
Product: glibc
Classification: Unclassified
Component: build (show other bugs)
Version: 2.36
: P2 normal
Target Milestone: 2.37
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-17 07:48 UTC by Letu Ren
Modified: 2022-08-26 11:25 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Letu Ren 2022-08-17 07:48:53 UTC
Hi, I'm building glibc on ArchLinux RISCV64 with a unmatched board. Test "misc/tst-glibcsyscalls" failed wierdly.

```
# cat misc/tst-glibcsyscalls.out 
error: kernel syscall 'memfd_secret' (447) not known to glibc
info: glibc tables are based on kernel version 5.18
info: installed kernel headers are version 5.18
```

My Linux kernel version is 5.18.3 and glibc version is 2.36.

Any advice about how to investigate this issue?
Comment 1 Letu Ren 2022-08-17 07:54:46 UTC
Add some environment information GCC 12.1.1 20220730, Binutils 2.39.
Comment 2 Andreas Schwab 2022-08-17 08:25:12 UTC
This was fixed by commit ac47d8f6cf.
Comment 3 Letu Ren 2022-08-17 08:34:24 UTC
Thanks, I'll backport that commit and rerun testsuite later.
Comment 4 Florian Weimer 2022-08-17 08:37:10 UTC
Fixed via:

commit fccadcdf5bed7ee67a6cef4714e0b477d6c8472c
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Tue Aug 2 21:05:07 2022 +0000

    Update syscall lists for Linux 5.19
    
    Linux 5.19 has no new syscalls, but enables memfd_secret in the uapi
    headers for RISC-V.  Update the version number in syscall-names.list
    to reflect that it is still current for 5.19 and regenerate the
    arch-syscall.h headers with build-many-glibcs.py update-syscalls.
    
    Tested with build-many-glibcs.py.
Comment 5 Letu Ren 2022-08-26 11:25:58 UTC
I've tested glibc which is checked out at e982657073c4db21459ffd9e17bc505b1d64b876, and this test doesn't fail. Thanks everyone who helped with this issue.