DEVICE/API: Fix segfault when releasing multiple exported batches on same endpoint #893
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Fix segmentation fault when releasing multiple exported batches on the same UCX endpoint.
Why?
Single
exported_batch
variable was overwritten by subsequent exports, causingreleaseBatch()
to use wrong batch handle. This caused crashes during elastic training when removing ranks with multiple active batches.How?
std::map<nixlUcxReq, ucp_batch_h>
to track multiple batch handlesmultipleExportReleaseSameEndpoint
that reproduces the bug