chore(fuzzing): extend syscall whitelist in sandbox fuzzers #3659
Conversation
This file contains 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
venkkatesh-sekar
changed the title
adambratschikaye
approved these changes
Jan 30, 2025
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.
In the sandbox monitor function, the parent thread calls
std::thread::sleep(std::time::Duration::from_secs(1))to allow the sandbox to spawn all its threads before tracing begins.However, this approach is unreliable—the sleep duration is arbitrary, and attachment can occur at any point in execution. This led to
getrandomfailures in CI.This PR removes the sleep timer and instead continuously fetches
tids as threads spawn, attaching to them dynamically. The trade-off is that it requires knowing the number of sandbox threads in advance.