Bug 2142111 - glibc: Restore IPC_64 support in sysvipc *ctl functions [rhel-9.1.0.z]
Summary: glibc: Restore IPC_64 support in sysvipc *ctl functions [rhel-9.1.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: glibc
Version: 9.2
Hardware: ppc64le
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florian Weimer
QA Contact: Sergey Kolosov
URL:
Whiteboard:
Depends On: 2141685
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-11 16:10 UTC by RHEL Program Management Team
Modified: 2023-07-18 14:29 UTC (History)
11 users (show)

Fixed In Version: glibc-2.34-40.el9_1.1
Doc Type: Bug Fix
Doc Text:
Cause: The msgctl, semctl, shmctl functions in glibc validate its command argument against a fixed list of values and fail if the command argument is not one of the known values. Consequence: Applications that pass the IPC_64 flag in addition to the actual command in the argument may fail because the combination is not recognized as a valid command. Fix: The command check is either removed (if unnecessary) or takes the IPC_64 flag into account. Result: Applications which pass the IPC_64 flag for compatibility with RHEL 7 glibc work again.
Clone Of: 2141685
Environment:
Last Closed: 2023-01-23 15:23:02 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-139199 0 None None None 2022-11-11 16:19:52 UTC
Red Hat Product Errata RHBA-2023:0342 0 None None None 2023-01-23 15:23:03 UTC

Comment 8 errata-xmlrpc 2023-01-23 15:23:02 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 (glibc 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/RHBA-2023:0342
Note You need to log in before you can comment on or make changes to this bug.