oxidecomputer / oxidecomputer/omicron
Audit: Are there cases where cancellation of a write could leak files?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
#10063 was the source issue.
This issue tracks:
- Are there cases where we are performing asynchronous {file,directory} operations which create new filesystem entries
- ... which could also be cancelled...
- ... but which could have side-effects which occur after cancellation?
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 reading source issue #10063 and the asynchronous file and directory operations described there. Trace operations that create filesystem entries and examine how cancellation is handled. Done means documenting whether any cancellation path can leave side effects after cancellation, including leaked files or directories.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100