Bug 1452814

Summary: glibc: [RFE][LLNL 8.1 FEAT] Create a mechanism within the dynamic linker where libraires are loaded at consistent addresses
Product: Red Hat Enterprise Linux 8 Reporter: Ben Woodard <woodard>
Component: glibcAssignee: glibc team <glibc-bugzilla>
Status: CLOSED WORKSFORME QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: ashankar, codonell, dj, fweimer, mnewsome, pfrankli, tgummels
Target Milestone: pre-dev-freezeKeywords: FutureFeature
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-27 09:41:13 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:
Bug Depends On:    
Bug Blocks: 1613559    

Description Ben Woodard 2017-05-19 17:20:11 UTC
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.

Comment 4 Florian Weimer 2019-08-27 09:41:13 UTC
“setarch -R” already supports this: https://manpages.debian.org/setarch