Investigate emulating SYS_futex during recording
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Followup to #673. We would need to work some magic with seccomp-bpf to allow us to distinguish entry to futex from entry to other syscalls, so that we could PTRACE_SYSEMU instead of PTRACE_SYSCALL the tracee into the call. But if we got that to work, emulating futex would avoid bugs like #673 (and the even worse hell that's going to break loose when we have to deal with robust futexes), and probably more importantly, gives us more control over thread scheduling.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #673 and the recording path that handles futex and other syscalls; the payload does not name specific files or tests. The work is complete when syscall entry can distinguish futex from other calls, futex can be emulated during recording, and thread scheduling gains the described control.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100