Fix invalid rogue peer delay request error #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When linuxptp goes from LISTENING to UNCALIBRATED, it will flush the the peer delay. This means that linuxptp forgets it sent a peer delay request. However, if there is an outstanding peer delay request at this point in time, the subsequent response will be considered rogue, and linuxptp will go into a faulty state. Which causes it to do nothing for a while. To fix this, we keep track of wether a flush_peer_delay has occurred. And if we receive a response after one, we don't consider it rogue but just ignore it. Signed-off-by: Joris Guisson <joris.guisson@luminex.be>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When linuxptp goes from LISTENING to UNCALIBRATED, it will flush the the peer delay. This means that linuxptp forgets it sent a peer delay request. However, if there is an outstanding peer delay request at this point in time, the subsequent response will be considered rogue, and linuxptp will go into a faulty state. Which causes it to do nothing for a while.
To fix this, we keep track of wether a flush_peer_delay has occurred. And if we receive a response after one, we don't consider it rogue but just ignore it.