Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
From https://bugzilla.redhat.com/show_bug.cgi?id=1432288
--- Comment #6 from Florian Weimer <fweimer> ---
(In reply to Ben Woodard from comment #5)
They really nead consistent library load addresses across compute nodes
participating in a compute job.
I'm not sure if we can actually support that in the long run. Everything is
moving towards adding more randomness.
------------
My response is:
This will ultimately end up becoming a dynamic linker feature request then. So please take that into account as you think about that section of code. Remember supercomputers are sort of like the borg or a bee hive and one of the things that keeps them operable is high levels of fractal like symmetry.
In the same way that genetic diversity protects a species from pathogens, randomization protects applications from exploits but as we can see from nature while most species have diversity on an individual level there are still a few like social bees and ants which maintain diversity on a colony or hive level as superorganisms.
There needs to be some sort of mechanism within the dynamic linker that allows all jobs participating in an MPI job to load their libraries in a consistent way. This is important for at least two reasons.
1) This greatly simplifies debugging and massively reduces the memory footprint used by MPI debuggers.
2) When using RDMA being able to pass data and actual pointers between the various ranks of the MPI job greatly simplifies and improves the performance of MPI jobs. When things have random offsets then all data and function pointers must be marshaled into offset and then translated to the other rank's address space. This extra step slows down interactions between compute nodes participating in the job.