fix(s2n-quic-core): flush packet queue between connections/MTU probes #1776
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
I noticed that some MTU probe packets were getting both
EMSGSIZE
andEINVAL
errors returned, depending on if the packet included a GSO segment or not. This causes extra flakiness for packets that are bundled with the MTU probe, since the whole packet is discarded on error.This change, instead, forces MTU probes to always be standalone packets. It does this by checking
can_gso
before writing the message and uses that value to know if it needs to be standalone or not.Before
After
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.