Use unsigned long for maxiterations, fixing undefined behavior in scan with extremely large count
#2414
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 one was found by afl++. Executing
scan 0 count nwith a count that is within 10% ofLONG_MAX,count * 10would causemaxiterationsto overflow. This is technically not a real problem since the waymaxiterationsis used would eventually cause it to underflow back toLONG_MAXagain and continue counting down from there but I figured we may want to fix this regardless for expected behavior correctness?