Rollback support for critical kernel operations
Open
Nobody has claimed this yet.
discussion
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
My understanding is that, at least for now, LiteBox kernel platforms' goal is not fail-safe. However, fail-fast is also not desired because one of our target platforms (e.g., cloud VMs) is critical.
#817
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 issue #817 and examining the kernel-platform failure behavior relevant to this request. The issue names no files, tests, or concrete rollback boundary, so the first step is to define the rollback semantics and affected critical operations. Done criteria should establish how failures avoid both fail-fast termination and unsafe partial state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100