RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1248454 [details]
patch

Description of problem:
The DOE has identified that software is the key to unlocking the potential of the next generation of supercomputing systems. To be able to facilitate this new generation of software, tools are needed. As a response LLNL is scaling up its tools team. These new hires and collaborators need better dynamic linker documentation since it is a primary interface for many kinds of tooling.

Here is a proposed patch which adds a chapter to the glibc manual. It has been submitted upstream but it hasn't been applied.

What is the problem with taking the attached patch first into upstream glibc and then backporting it rhel? It is a doc only patch and so the risk is very low.

If you need changes to the patch please speak up and identify what needs to be changed.

Created attachment 1314527 [details]
Update the patch to the latest glibc git

This patch applies cleanly to the latest glibc git.

We are going to track this upstream here:
"Bug 25595 - Impove the quality of dynamic linker documentation"
https://sourceware.org/bugzilla/show_bug.cgi?id=25595

This bug is now CLOSED/UPSTREAM and we'll triage this upstream and get it integrated there.

These issues will then naturally become a part of the next version of RHEL. We may review CLOSED/UPSTREAM bugs for backport.