Native Android Seccomp Limitations
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, cpp, linux
- Domain
- devtools, operating-systems
Research direction
No files, tests, or entry points are identified in the issue. First trace rr's syscall handling and recording paths on native Android, then determine whether SIGSYS handling can preserve inspection and replay behavior. Done means rr no longer fails immediately on Android's invalid-syscall restrictions without breaking recording or inspection.
Written by the indexing model from the issue text.
Description
Because rr uses its "own syscalls", rr encounters immediate runtime failures from bad syscalls on native Android devices (e.g., within Termux).
While Android does support seccomp filtering, its security model (since Android OS 8) only allows filtering of valid syscalls. Invalid numbers will cause SIGSYS regardless of seccomp filtering.
It's still possible to setup signal/exception handlers and capture SIGSYS, so I thought about attempting this; however, I'm not familiar enough with rr's codebase, and whether that would break how rr inspects, records, etc., and did not want to waste time implementing something if so.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
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.
More from rr-debugger/rr
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rr-debugger/rr#4096 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rr-debugger/rr#4093 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rr-debugger/rr#4090 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
rr-debugger/rr#4060 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
rr-debugger/rr#4059 · 1 comment ·
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·