Skip to content

Lazy intialization of frameworks is not thread safe #9307

Open
@nysal

Description

@nysal

Thank you for taking the time to submit an issue!

Background information

What version of Open MPI are you using? (e.g., v3.0.5, v4.0.2, git branch name and hash, etc.)

master

Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)

git

If you are building/installing from a git clone, please copy-n-paste the output from git submodule status.

cf79874 3rd-party/openpmix (v1.1.3-3057-gcf79874b)
91b235f3c0d9be9abde7d79de70e6996fb08adba 3rd-party/prrte (psrvr-v2.0.0rc1-3954-g91b235f3c0)

Please describe the system on which you are running

  • Operating system/version: RHEL 8.4
  • Computer hardware: x86_64
  • Network type: Ethernet

Details of the problem

Please describe, in detail, the problem that you are having, including the behavior you expect to see, the actual behavior that you are seeing, steps to reproduce the problem, etc. It is most helpful if you can attach a small program that a developer can use to reproduce your problem.

Opening a new issue based on discussions in #9302
George suggested a more unified approach for thread safe lazy initialization of frameworks.
We can use this issue to arrive at a consensus on how this should look like.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions