Skip to content

v4.1.x: Protect the pmix3x component from a PMIx v4 attribute #9213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 11, 2021
Merged

v4.1.x: Protect the pmix3x component from a PMIx v4 attribute #9213

merged 1 commit into from
Aug 11, 2021

Conversation

rhc54
Copy link
Contributor

@rhc54 rhc54 commented Aug 10, 2021

PMIx v4 introduced a new PMIX_TOPO2 attribute that takes a data type
unknown to PMIx 3. Unfortunately, that attribute can be provided by
the RM without our knowledge. We will update PMIx to try and detect
it and prevent it from slipping down to this level. Meantime, add
some simple protection here.

Thanks to @amckinstry for the report and the base patch.

Fixes #8596

Signed-off-by: Ralph Castain [email protected]
bot:notacherrypick

PMIx v4 introduced a new PMIX_TOPO2 attribute that takes a data type
unknown to PMIx 3. Unfortunately, that attribute can be provided by
the RM without our knowledge. We will update PMIx to try and detect
it and prevent it from slipping down to this level. Meantime, add
some simple protection here.

Signed-off-by: Ralph Castain <[email protected]>
@jsquyres jsquyres merged commit a39a051 into open-mpi:v4.1.x Aug 11, 2021
@rhc54 rhc54 deleted the rfc41/pmix3 branch October 20, 2021 02:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants