oxidecomputer / oxidecomputer/propolis
Address virtio block virtqueue error handling todo
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
A buggy/malicious virtio block driver could crash a propolis instance.
Contributor guide
No contributing guide indexed for this repository
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 at lib/propolis/src/hw/virtio/block.rs lines 140-144 and trace the virtqueue error-handling path. Review the surrounding virtio block implementation and existing tests, then verify that malformed or malicious driver input no longer crashes a propolis instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100