Bug 1871386 - glibc: Update syscall names for Linux 5.6, 5.7, and 5.8.
Summary: glibc: Update syscall names for Linux 5.6, 5.7, and 5.8.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Patsy Griffin
QA Contact: Sergey Kolosov
URL:
Whiteboard:
: 1902258 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-23 01:37 UTC by Carlos O'Donell
Modified: 2023-07-18 14:30 UTC (History)
8 users (show)

Fixed In Version: glibc-2.28-152.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:28:09 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4358 0 None None None 2021-11-09 19:28:32 UTC

Description Carlos O'Donell 2020-08-23 01:37:06 UTC
Backport the following commits to update Linux syscall names:

e788beaf093bfafecd6b4456b984bd927c18987a
Update syscall lists for Linux 5.6.

b67339d0bbc07911859ca8c488e1923441cd3c33
Update syscall-names.list for Linux 5.7.

1cfb4715288845ebc55ad664421b48b32de9599c
Update syscall lists for Linux 5.8.

Comment 2 Carlos O'Donell 2020-11-27 15:04:41 UTC
*** Bug 1902258 has been marked as a duplicate of this bug. ***

Comment 3 Florian Weimer 2020-11-27 15:04:42 UTC
The lack of a syscall list update results in misc/tst-syscall-list failure due to the kernel system call backport in bug 1333764.

Comment 11 errata-xmlrpc 2021-11-09 19:28:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: glibc security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4358


Note You need to log in before you can comment on or make changes to this bug.