-
Notifications
You must be signed in to change notification settings - Fork 6k
br: Use int for vlen to prevent overflow (#63662) #63676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
br: Use int for vlen to prevent overflow (#63662) #63676
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-8.5 #63676 +/- ##
================================================
Coverage ? 57.8206%
================================================
Files ? 1783
Lines ? 632962
Branches ? 0
================================================
Hits ? 365983
Misses ? 242260
Partials ? 24719
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
/run-mysql-test |
1 similar comment
/run-mysql-test |
@RidRisR: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: 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. |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BornChanger, Leavrth, RidRisR The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
This is an automated cherry-pick of #63662
What problem does this PR solve?
Issue Number: close #63663
Problem Summary:
What changed and how does it work?
Change vlen to int before use it as a length flag to avoid parse overflow.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.