Bug 2149994

Summary: glibc: Earlier removal of alternative multilibs
Product: Red Hat Enterprise Linux 9 Reporter: Florian Weimer <fweimer>
Component: glibcAssignee: Tulio Magno Quites Machado Filho <tuliom>
Status: CLOSED ERRATA QA Contact: Sergey Kolosov <skolosov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.2CC: ashankar, codonell, dj, fweimer, markobri, mnewsome, pfrankli, sipoyare, skolosov, tuliom
Target Milestone: rcKeywords: Bugfix, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.34-57.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:16:03 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:

Description Florian Weimer 2022-12-01 14:37:29 UTC
We currently remove the multilibs in %post, but we could do this earlier, in %pre. This is related to bug 2119304.

With the removal in %post, we have this issue: /lib64/glibc-hwcaps comes before /lib64/ld*, so RPM upgrades to the new version of libc.so.6 before ld.so. This means there is a window during the upgrade where new processes run with new libc.so.6 and old ld.so.

Without multilibs, /lib64/ld* comes before /lib64/lib*, and the possible race/version mismatch involves an old libc.so.6 with a new ld.so. Empirically, it is easier to evolve the GLIBC_PRIVATE ABI to better support this mismatch, so we should align the multilib case to this. This improves the upgrade experience at the expense of the downgrade experiences (but of course updates are more common because there has to be an upgrade before there can be a downgrade).

Comment 5 errata-xmlrpc 2023-05-09 08:16:03 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:2481