Skip to content

btl/vader: ensure that the send tag is always written last#5696

Merged
hjelmn merged 1 commit intoopen-mpi:masterfrom
hjelmn:vader_5375
Sep 14, 2018
Merged

btl/vader: ensure that the send tag is always written last#5696
hjelmn merged 1 commit intoopen-mpi:masterfrom
hjelmn:vader_5375

Conversation

@hjelmn
Copy link
Copy Markdown
Member

@hjelmn hjelmn commented Sep 14, 2018

To ensure fast box entries are complete when processed by the
receiving process the tag must be written last. This includes a zero
header for the next fast box entry (in some cases). This commit fixes
two instances where the tag was written too early. In one case, on
32-bit systems it is possible for the tag part of the header to be
written before the size. The second instance is an ordering issue. The
zero header was being written after the fastbox header.

Fixes #5375, #5638

Signed-off-by: Nathan Hjelm [email protected]

To ensure fast box entries are complete when processed by the
receiving process the tag must be written last. This includes a zero
header for the next fast box entry (in some cases). This commit fixes
two instances where the tag was written too early. In one case, on
32-bit systems it is possible for the tag part of the header to be
written before the size. The second instance is an ordering issue. The
zero header was being written after the fastbox header.

Fixes open-mpi#5375, open-mpi#5638

Signed-off-by: Nathan Hjelm <[email protected]>
@jsquyres
Copy link
Copy Markdown
Member

In talking to @hjelmn in IM, he points out that this bug is not silent data corruption, but rather will just cause a hang or crash. It's still a pretty serious bug, but at least it's not silent data corruption.

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.

Vader BTL segfaults, sm okay

2 participants