Bug 2115828

Summary:	glibc: Backport __rseq_* symbols from glibc 2.35 [rhel-9.0.0.z]
Product:	Red Hat Enterprise Linux 9	Reporter:	RHEL Program Management Team <pgm-rhel-tools>
Component:	glibc	Assignee:	Florian Weimer <fweimer>
Status:	CLOSED ERRATA	QA Contact:	Martin Coufal <mcoufal>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.1	CC:	ashankar, codonell, dj, fweimer, mcoufal, mnewsome, pfrankli, sipoyare, skolosov
Target Milestone:	rc	Keywords:	Patch, Triaged, ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
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.	Story Points:	---
Clone Of:	2085529	Environment:
Last Closed:	2022-09-20 14:11:14 UTC	Type:	---
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:	2085529
Bug Blocks:

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