Skip to content

mctpd: improve handling for out-of-spec Set Endpoint ID responses #83

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
Jun 25, 2025

Conversation

jk-ozlabs
Copy link
Member

We may have endpoints reporting strange EID values in their set endpoint ID response, even when reporting that the assignement was accepted. Particularly, if the EID is in the invalid range, we will still attempt to add neighour and route entries for this invalid EID.

We still want to accommodate valid IDs that were not the same as the one assigned, but ensure the EID is valid before processing.

We may have endpoints reporting strange EID values in their set endpoint
ID response, even when reporting that the assignement was accepted.
Particularly, if the EID is in the invalid range, we will still attempt
to add neighour and route entries for this invalid EID.

We still want to accommodate valid IDs that were not the same as the one
assigned, but ensure the EID is valid before processing.

Signed-off-by: Jeremy Kerr <[email protected]>
@jk-ozlabs jk-ozlabs force-pushed the pr/set-eid-response-handling branch from 9b7f022 to 2948041 Compare June 18, 2025 11:28
@jk-ozlabs jk-ozlabs merged commit 2948041 into main Jun 25, 2025
2 checks passed
@jk-ozlabs jk-ozlabs deleted the pr/set-eid-response-handling branch June 25, 2025 03:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants