Skip to content

QUIC: retire packets acked after their sent path was torn down - #256

Open
kkuk24 wants to merge 1 commit into
mainfrom
kkuk/fix-ack-after-path-teardown
Open

kkuk24 wants to merge 1 commit into
mainfrom
kkuk/fix-ack-after-path-teardown

Conversation

@kkuk24

@kkuk24 kkuk24 commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

ACKs for packets sent on a path that has since been removed, such as the old path after a migration, were dropped before packetAcked ran. The in-flight count never went down, so the PTO timer was re-armed forever, and the packets' contents were never acknowledged. Retire them anyway, skipping only the steps that need the path.

@kkuk24 kkuk24 added the 🔨 semver/patch No public API change. label Oct 14, 2026
@agnosticdev

Copy link
Copy Markdown
Collaborator

Does the in-flight counter go down now in Recovery?

ACKs for packets sent on a path that has since been removed, such as
the old path after a migration, were dropped before packetAcked ran.
The in-flight count never went down, so the PTO timer was re-armed
forever, and the packets' contents were never acknowledged. Retire
them anyway, skipping only the steps that need the path.
@kkuk24
kkuk24 force-pushed the kkuk/fix-ack-after-path-teardown branch from 085221a to ca81093 Compare October 28, 2026 20:25
@kkuk24

kkuk24 commented Oct 28, 2026

Copy link
Copy Markdown
Contributor Author

Does the in-flight counter go down now in Recovery?

Yes it goes down now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🔨 semver/patch No public API change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants