Skip to content
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

fix: remove debug assert that requires ordered acks for non mtu probe acks #1888

Closed
wants to merge 1 commit into from

Conversation

tthebst
Copy link
Contributor

@tthebst tthebst commented Jun 6, 2024

Non-probe acks can be out of order. As of my understanding the ordering is only given for probe acks.

To confirm: Should it also be removed for probe acks?

fixes #1889

@tthebst tthebst changed the title fix: remove debug assert that required ordered acks for non mtu probe acks fix: remove debug assert that requires ordered acks for non mtu probe acks Jun 6, 2024
@@ -26,6 +26,12 @@ async fn run_server(addr: SocketAddr) {
// accept a single connection
let incoming_conn = endpoint.accept().await.unwrap();
let conn = incoming_conn.await.unwrap();

loop {
Copy link
Member

Choose a reason for hiding this comment

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

These changes seem unrelated?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep. Sorry. Pushed my test changes by accident.

@Ralith
Copy link
Collaborator

Ralith commented Jun 6, 2024

This assert exists because the following code relies on that assumption for correctness. We need to study how this is occurring and adjust ACK processing and/or MTU detection logic accordingly.

@tthebst tthebst closed this Jun 7, 2024
@tthebst
Copy link
Contributor Author

tthebst commented Jun 7, 2024

I would be willing to help debug this if you need help lmk.

@djc
Copy link
Member

djc commented Jun 7, 2024

Any help would be appreciated, maybe you can have a read through the code and see if you can come up with a change proposal? Also a regression test that catches this would be good.

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.

ACKs are delivered in order panic when packets are reordered
3 participants