oxidecomputer / oxidecomputer/opte
Audit panic behavior
Open
Nobody has claimed this yet.
mvp
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
We need to run through all calls like unwrap(), expect(), panic!(), etc, that are explicit panic points. We want to make sure we're not panicking the host unless it's really, truly an egregious bug in OPTE.
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 searching the repository for explicit panic points such as unwrap(), expect(), and panic!(). Review each call in the context of OPTE's packet-processing behavior and determine whether it can panic the host. Done means the explicit panic points have been audited and only truly egregious host-panic cases remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100