Use raw syscalls to avoid sporadic hangs#2425
Merged
utam0k merged 1 commit intoyouki-dev:mainfrom Oct 12, 2023
Merged
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2425 +/- ##
==========================================
- Coverage 66.01% 65.93% -0.08%
==========================================
Files 133 133
Lines 16832 16851 +19
==========================================
Hits 11111 11111
- Misses 5721 5740 +19 |
Signed-off-by: Jorge Prendes <jorge.prendes@gmail.com>
e2f05e0 to
32ffc4d
Compare
Member
|
@jprendes I appreciate your investigation and PR. Have you checked if this patch worked fine for runwasi? |
Contributor
Author
|
@utam0k it seems to work. It is difficult to say as the original issue is sporadic. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
setgroups/setresgid/setresuidfunctions innix/libcare not safe to call afterclone/clone3.These function use a blocking mechanism that synchronises across all threads in the process.
To do this
libc(glibc/musl) needs to do some bookkeeping, which breaks on the new process afterclone.See the discussion in containerd/runwasi#347 for more details.
This PR worksaround that issue by using raw syscalls for
setgroups/setresgid/setresuid.This is generally not safe, as the raw syscalls only affect the calling thread and not the whole process.
It is safe to do so in this case because at the point when they are called in libcontainer the init process only has one thread.