Bug 1439165

Summary: glibc: SYS_getrandom definition missing on s390x
Product: Red Hat Enterprise Linux 7 Reporter: Florian Weimer <fweimer>
Component: glibcAssignee: Florian Weimer <fweimer>
Status: CLOSED ERRATA QA Contact: Sergey Kolosov <skolosov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: ashankar, codonell, fweimer, mcermak, mnewsome, pfrankli, skolosov
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
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 18:11:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1432218, 1484729    
Bug Blocks: 1413146    

Description Florian Weimer 2017-04-05 11:07:02 UTC
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 19:44:25 UTC
Patch posted upstream:


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 18:11:55 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, and where to find the updated
files, follow the link below.

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