Implement clone3
fallback to clone
when ENOSYS returns
#2081
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.
Fix #2030
Potentially controversial:
clone3
crate. Our usecase for the clone3 syscall is very specific and do not need to support everything. I can easily replace the clone3 crate with a few lines of code, so I did it in this PR. We usually favors safe syscall wrappers likenix
overlibc
, but I believe the save is worth it here.clone
syscall instead ofglibc
wrapper. Details are in the comments.Otherwise, this PR does what the RFC outline. Unit tests using seccomp profile to simulate clone3 being blocked are added.
Also, I implemented fallback for
ENOSYS
only. Technically, we can addEPERM
to the list as well.