Bug 2115828 - glibc: Backport __rseq_* symbols from glibc 2.35 [rhel-9.0.0.z]
Summary: glibc: Backport __rseq_* symbols from glibc 2.35 [rhel-9.0.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: glibc
Version: 9.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Florian Weimer
QA Contact: Martin Coufal
URL:
Whiteboard:
Depends On: 2085529
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-05 13:52 UTC by RHEL Program Management Team
Modified: 2023-07-18 14:29 UTC (History)
9 users (show)

Fixed In Version: glibc-2.34-28.el9_0.1
Doc Type: Enhancement
Doc Text:
Feature: Compatibility with rseq symbols from RHEL 9.1 glibc Reason: In Red Hat Enterprise Linux 9.1, glibc adds additional rseq-related symbols from the upstream glibc 2.35 version. If applications use these symbols, they will not launch on Red Hat Enterprise Linux 9.0. Result: With these symbols added, applications built against RHEL 9.1 glibc will start even if they use rseq. Note that rseq registration remains disabled by default in RHEL 9.0 for compatibility reasons, but it can be enabled using the glibc.pthread.rseq=1 tunable.
Clone Of: 2085529
Environment:
Last Closed: 2022-09-20 14:11:14 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-130389 0 None None None 2022-08-05 13:55:27 UTC
Red Hat Product Errata RHBA-2022:6605 0 None None None 2022-09-20 14:11:18 UTC

Comment 1 Florian Weimer 2022-08-05 13:59:00 UTC 
We are only going to add the symbols __rseq_offset, __rseq_size, __rseq_flags, so that 9.0 remains compatible with binaries built on 9.1. This change should NOT change the rseq default (as we did in 9.1). Instead rseq remains disabled by default.
Comment 8 errata-xmlrpc 2022-09-20 14:11:14 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-2022:6605
Note You need to log in before you can comment on or make changes to this bug.