Bug 1592475

Summary: glibc headers: add ipc STAT_ANY constants
Product: Red Hat Enterprise Linux 7 Reporter: Joe Lawrence <joe.lawrence>
Component: glibcAssignee: Arjun Shankar <ashankar>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.6CC: aarnold, ashankar, codonell, dj, fweimer, joe.lawrence, mcermak, mnewsome, pfrankli, salmy, skolosov, tgummels
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.17-272.el7 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 12:49:05 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1643040    

Description Joe Lawrence 2018-06-18 15:25:49 UTC
Description of problem:
Linux 4.17 added _ANY variants to the SHM_STAT, SEM_STAT, and MSG_STAT ipc command constants.  Those kernel commits have been requested to be backported to RHEL-7.6 (bz1579402) and as such, would require an accompanying glibc-headers change.

Additional info:
These constants have already been added to the upstream glibc project with the following commits:

  f2857da7cdb6 Add SHM_STAT_ANY from Linux 4.17 to bits/shm.h.
  176c7fee517c Add SEM_STAT_ANY from Linux 4.17 to bits/sem.h.
  86bf0019ed9c Add MSG_STAT_ANY from Linux 4.17 to bits/msq.h.

Thanks, --- Joe

Comment 14 Arne Arnold 2018-07-11 01:13:11 UTC
Hi colleagues,

fine with me for the reasons mentioned above (build vs. runtime).

Arne

Comment 16 Sergey Kolosov 2019-06-10 09:54:04 UTC
Verified,
glibc-2.17-272.el7 contains corresponding SHM_STAT_ANY, SEM_STAT_ANY, and MSG_STAT_ANY ipc command constants.

Comment 18 errata-xmlrpc 2019-08-06 12:49:05 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.

https://access.redhat.com/errata/RHSA-2019:2118