Skip to content

prov/sockets: fix rx_buffered arrived befor fi_av_insert - #11037

Closed
hzhou wants to merge 1 commit into
ofiwg:mainfrom
hzhou:2505_sock_rx
Closed

prov/sockets: fix rx_buffered arrived befor fi_av_insert#11037
hzhou wants to merge 1 commit into
ofiwg:mainfrom
hzhou:2505_sock_rx

Conversation

@hzhou

@hzhou hzhou commented May 16, 2025

Copy link
Copy Markdown
Contributor

When an unexpected message arrive before fi_av_insert, the av_index won't be available and was set to FI_ADDR_NOTAVAIL. It eventually may get mismatched to a wrong receive entry. Store the raw ip address for this case and try to recover the av_index at match time.

This bug is triggered in MPICH recent CI testing after we revamped support for MPI Sessions. With world model, we have a barrier at the end of MPI_Init, preventing messages to arrive before all fi_av_inserts completes. With sessions, we no longer have such barriers.

When an unexpected message arrive before fi_av_insert, the av_index
won't be available and was set to FI_ADDR_NOTAVAIL. It eventually may
get mismatched to a wrong recv entry. Store the raw ip address for this
case and try to recover the av_index at match time.

Signed-off-by: Hui Zhou <hzhou321@anl.gov>
}
rx_posted = sock_rx_get_entry(rx_ctx, rx_buffered->addr,
rx_buffered->tag,
rx_buffered->is_tagged);

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: do we allow FI_ADDR_NOTAVAIL to be matched? If so, what is the use case?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be allowed. The posted recv may not care who the sender is (i.e. rx_entry->addr == FI_ADDR_UNSPEC).

@github-actions

Copy link
Copy Markdown
Contributor

This pull request is stale because it has been open 360 days with no activity. Remove stale label or comment, otherwise it will be closed in 7 days.

@github-actions github-actions Bot added the stale label May 15, 2026
@github-actions github-actions Bot closed this May 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants