bug fix of poptrie6_lookup. patches to test code (to see a failure), and the fix.#33
Open
yasuhironet wants to merge 2 commits intopixos:masterfrom
Open
bug fix of poptrie6_lookup. patches to test code (to see a failure), and the fix.#33yasuhironet wants to merge 2 commits intopixos:masterfrom
yasuhironet wants to merge 2 commits intopixos:masterfrom
Conversation
added 2 commits
July 6, 2017 20:46
/128 route causes a problem. Not sure if the prefix contents value is related, but I see sometimes fe80::XXXX/128 works fine. If we change the /128 to /127, it should pass.
stride exceeds the end of the address, so we need to consider the case to stride exceeding the address (128 bits). (the last part is 126 + 6 = 132, 126-131 bits)
yasuhironet
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This change will make the IPv6 route add test fail. It seems that the
/128 route causes a problem. Not sure if the prefix contents value
is related, but I see sometimes fe80::XXXX/128 works fine.
If we change the /128 to /127, it should pass.