Skip to content

fix: atomic operations on 32-byte device #3029

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

Merged
merged 1 commit into from
Dec 26, 2021
Merged

Conversation

jonyhy96
Copy link
Contributor

@jonyhy96 jonyhy96 commented Dec 13, 2021

xref: kubernetes/kubernetes#106977

prevent panic on atomic operations

@k8s-ci-robot
Copy link
Collaborator

Hi @jonyhy96. Thanks for your PR.

I'm waiting for a google member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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/test-infra repository.

@mikhail-sakhnov
Copy link

@jonyhy96 fyi, I tried using the same patch in k0sproject release for 1.23 (k0sproject/k0s@953909e) it seems to be working on armv7, at least kubelet doesn't panic and generally passed our test suite.

@brandond
Copy link

Will be using this for K3s as well.

@iwankgb
Copy link
Collaborator

iwankgb commented Dec 24, 2021

/ok-to-test

@iwankgb
Copy link
Collaborator

iwankgb commented Dec 26, 2021

/approve

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants