[tock] Tock kernel-userspace isolation test.
Open
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
We should have a Tock test that verifies userspace processes cannot access any data they are not supposed to access. To test this, we can create test apps that attempt unauthorized accesses (reads and writes to kernel and MMIO memory regions) and verify that those accesses result in application faults.
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 locating the Tock kernel and userspace test-app entry points in the OpenTitan tree, then review how existing application faults are verified. Add coverage for unauthorized reads and writes to kernel and MMIO memory regions, with completion shown by faults being observed for each attempted access.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, security, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100