fix(update): avoid update resource while the process is zombie #393
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
add a check in zombie init process.
If update task between the wait_pid call and init exit. The bug will occur, the cgroup maybe update the root's cgroup path.
Because the cgroup path has been recycled by system ,but the wait_pid haven't recycled the resource of the process. The update task is processing.
A easy way to reproduce this bug. Occasionally triggered in high concurrency scenarios.
crictl run --no-pull container-config.json pod.json
(gdb) handle SIGCHLD ignore
(gdb) continue
the init process will become zombie , you can send update task to the shim ,but the cgroup path is not correct.