-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
fix negative slice index error in keymutex in 1.13 #74386
Conversation
/assign @aleksandra-malinowska |
/cc @apelisse |
/sig storage |
Please get approve and LGTM as for any other PR. |
/lgtm |
/assign @thockin |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: apelisse, danielqsj, thockin 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 |
…386-upstream-release-1.12 Automated cherry pick of #74386: fix negative slice index error in keymutex
What type of PR is this?
/kind bug
What this PR does / why we need it:
This issue #73858 report that the generated index for slice in
keymutex
maybe negative in some platform (like arm).This PR aims to fix this issue.
Which issue(s) this PR fixes:
Fixes #73858
Special notes for your reviewer:
Already fixed it in master branch by kubernetes/utils#84.
But in before
1.14
, keymutex code is in k/k, so I submit this PR to fix it in1.13
, and then will cherrypick to1.12
.Does this PR introduce a user-facing change?: