conncache: prevent theoretical overflow in maxconnects calculation #19271
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 no explicit maxconnects is set, the connection pool limit is calculated as 4 times the number of running transfers.
The multiplication
running * 4could theoretically overflow if the number of running transfers exceeds UINT_MAX/4.While this scenario is highly unlikely in practice due to system resource limitations, this fix is minimal and follows defensive programming principles to ensure robustness in theoretical edge cases.