oxidecomputer / oxidecomputer/propolis
Enforce block transfer size limits
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
It is unreasonable to allow guests to make block IO requests of unbounded sizes. We should permit the backends to specify a maximum allowed size, communicating it up through the frontend where possible. In addition to that, we can make smarter buffering decisions armed with said maximum size.
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
No files or tests are named. Start by tracing the block I/O request path and the backend/frontend interfaces that carry request sizes. Done means backends can specify a maximum size, the frontend communicates it where possible, and buffering decisions use that limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100