Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1439165 - glibc: SYS_getrandom definition missing on s390x
glibc: SYS_getrandom definition missing on s390x
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Florian Weimer
Sergey Kolosov
: Patch
Depends On: 1432218 1484729
Blocks: 1413146
  Show dependency treegraph
 
Reported: 2017-04-05 07:07 EDT by Florian Weimer
Modified: 2017-08-24 04:45 EDT (History)
7 users (show)

See Also:
Fixed In Version: glibc-2.17-194.el7
Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 14:11:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1916 normal SHIPPED_LIVE Moderate: glibc security, bug fix, and enhancement update 2017-08-01 14:05:43 EDT

  None (edit)
Description Florian Weimer 2017-04-05 07:07:02 EDT
glibc-2.17-192.el7 was built against an older kernel version which did not backport the getrandom system call to all architectures (see bug 1432218).  As a result, SYS_getrandom is not defined on all architectures.  In particular, it is missing on s390x.

The reason that glibc, at build time, obtains a list of the __NR_* macros from the kernel headers and synthesized its list of SYS_* macros from that.  This means that if newer kernel headers are installed at a later point, an extended __NR_* macro list will not make it into corresponding SYS_* macros.

We need to rebuild glibc (with a new NVR) against newer kernel headers, once bug 1432218 is fixed.  I'll work on an alternative approach upstream which eliminates the build ordering dependency.
Comment 1 Florian Weimer 2017-04-05 15:44:25 EDT
Patch posted upstream:

https://sourceware.org/ml/libc-alpha/2017-04/msg00082.html

When we backport this, we should put the system call list into a separate, top-level file which goes directly into the SRPM, so that it is simpler to update in each y-stream release.
Comment 9 errata-xmlrpc 2017-08-01 14:11:55 EDT
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, 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-2017:1916

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