br: fix potential overflow issues

[RidRisR]

What problem does this PR solve?

Issue Number: close #64222

Problem Summary:

Fix the potential overflow issues

What changed and how does it work?

Use Claude to scan all files under br dir, find all potential overflow issues and fix them (with human double check) one by one.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @RidRisR. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 60 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.0581%. Comparing base (d7470ff) to head (0bf6b05).
⚠️ Report is 48 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #64219        +/-   ##
================================================
+ Coverage   72.7344%   73.0581%   +0.3237%     
================================================
  Files          1853       1881        +28     
  Lines        500569     524415     +23846     
================================================
+ Hits         364086     383128     +19042     
- Misses       114348     118323      +3975     
- Partials      22135      22964       +829     

Flag	Coverage Δ
integration	44.5597% <0.0000%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.8700% <ø> (ø)
parser	∅ <ø> (∅)
br	46.2976% <0.0000%> (-0.1139%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign leavrth for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• br/OWNERS
• br/pkg/storage/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

@RidRisR: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/mysql-test	0bf6b05	link	true	/test mysql-test
pull-unit-test-next-gen	0bf6b05	link	true	/test pull-unit-test-next-gen
pull-br-integration-test	0bf6b05	link	true	/test pull-br-integration-test
idc-jenkins-ci-tidb/unit-test	0bf6b05	link	true	/test unit-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.