Skip to content

cgroup: retry file writes on EINTR errors #3170

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

Closed
wants to merge 1 commit into from

Conversation

copybara-service[bot]
Copy link

cgroup: retry file writes on EINTR errors

After deploying a version of gvisor built with Go 1.14, we're seeing errors setting up cgroups (we manually run runsc via runsc run, which creates the cgroup). This turns out to be a known issue with Go: golang/go#38033. Given that the fix won't be backported, we should retry writes that may fail with EINTR.

This is also what runc does: opencontainers/runc#2258

FUTURE_COPYBARA_INTEGRATE_REVIEW=#3102 from stripe:andrew/cgroup-eintr 079123b

@copybara-service copybara-service bot force-pushed the test/cl320183771 branch 2 times, most recently from b627219 to 36c9179 Compare July 8, 2020 17:48
@googlebot googlebot added the cla: yes CLA has been signed label Jul 8, 2020
After deploying a version of gvisor built with Go 1.14, we're seeing errors setting up cgroups (we manually run `runsc` via `runsc run`, which creates the cgroup). This turns out to be a known issue with Go: golang/go#38033. Given that the [fix won't be backported](golang/go#39026 (comment)), we should retry writes that may fail with EINTR.

This is also what runc does: opencontainers/runc#2258

FUTURE_COPYBARA_INTEGRATE_REVIEW=#3102 from stripe:andrew/cgroup-eintr 079123b
PiperOrigin-RevId: 320183771
@copybara-service copybara-service bot closed this Jul 15, 2020
@copybara-service copybara-service bot deleted the test/cl320183771 branch July 15, 2020 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes CLA has been signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants