-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Crio crashed with a concurrent map read and map write race condition #6321
Comments
in the stacktrace, does it show the other routine? I am only able to see one (though I may be misreading) |
@haircommander Here is the full stacktrace |
A friendly reminder that this issue had no activity for 30 days. |
Closing this issue since it had no activity in the past 90 days. |
A friendly reminder that this issue had no activity for 30 days. |
Closing this issue since it had no activity in the past 90 days. |
A friendly reminder that this issue had no activity for 30 days. |
Closing this issue since it had no activity in the past 90 days. |
What happened?
Crio crashed with the following panic
What did you expect to happen?
Crio not to crash with a race condition
How can we reproduce it (as minimally and precisely as possible)?
Since this is a race condition, I cannot provide steps to reproduce the issue
Anything else we need to know?
The problem seems to be associated with lack of locks in the Project Quota file which used by cri-o as a dependency. The functions that let the user know the value of XFS quotas does not seem to be thread safe. An issue was created in the library too
CRI-O and Kubernetes version
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)
The text was updated successfully, but these errors were encountered: