Skip to content

Handle sending path challenge on paths that have not resolved route yet#3545

Merged
csujedihy merged 2 commits into
mainfrom
huanyi/path-challenge
Apr 4, 2023
Merged

Handle sending path challenge on paths that have not resolved route yet#3545
csujedihy merged 2 commits into
mainfrom
huanyi/path-challenge

Conversation

@csujedihy

Copy link
Copy Markdown
Collaborator

Description

It's possible that when sending a path challenge, the route is not yet resolved. We need to pause and resume path challenge when that happens.

Testing

CI

@csujedihy csujedihy requested a review from a team as a code owner April 1, 2023 00:39
@csujedihy

Copy link
Copy Markdown
Collaborator Author

Will take a look at the failures when I am back on Tuesday or Wednesday

@csujedihy csujedihy added Area: Core Related to the shared, core protocol logic Area: Lola Related to low latency work labels Apr 4, 2023
Comment thread src/core/send.c

#ifdef QUIC_USE_RAW_DATAPATH
//
// Make sure the route is resolved before sending the path challenge.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Any ideas on how? Could we make a test to explicitly trigger this?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

You meant how a route is not resolved before sending the path challenge? Isn't this already covered by existing address rebind test cases? When we create a new path upon seeing a different source address from the peer, we create a path with an unresolved route.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Ok.

@csujedihy csujedihy merged commit d34b095 into main Apr 4, 2023
@csujedihy csujedihy deleted the huanyi/path-challenge branch April 4, 2023 23:11
@nibanks

nibanks commented Apr 5, 2023

Copy link
Copy Markdown
Collaborator

@csujedihy wasn't there a bug that could be closed along with this?

@nibanks nibanks linked an issue Apr 5, 2023 that may be closed by this pull request
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: Core Related to the shared, core protocol logic Area: Lola Related to low latency work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sending path challenge could trigger an assert in CxPlatSocketSend

2 participants