WIP: Define original-device durability and undo journaling #2
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-block!2
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/posix-compat"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary and rationale
Define explicit original-device durability barriers and an allocation-free undo journal over caller-selected storage. Preserve exact transport correlation, original backend custody and unsuppressible storage uncertainty.
Tracking and scope
The linked component audit, implementation and consumer requirements remain part of this WIP review. The phase-wide guest and toolchain build requirements stay with the phase completion issue.
Architecture, authority and failure behavior
The durability contract describes support without granting device authority. Clients use only the supplied transport, validate complete correlation and never replay an accepted request. Providers refuse unsupported guarantees.
The original-device undo journal owns the caller's backend, target/log extents and actual journal capacity. Complete counted-prefix admission precedes writes. Reverse restoration, ordered barriers and retained storage uncertainty govern terminal outcomes; unwind guards close access without destructor I/O. No heap allocation, ambient provider selection or hidden journal capacity is introduced.
FAT format/provider integration and complete consumer, runtime and guest acceptance remain open. Signed dependency coordination preserves original source selection.
Validation evidence
Formatting, strict Clippy, warning-denied builds and documentation, unit tests, and applicable native/VM and consumer regressions remain required for the declared scope. Authored controls and older successful runs do not establish current full acceptance.
Review checklist
This review remains WIP until its declared scope and dependent requirements are complete.
erikinkinen referenced this pull request from erix/posixd2026-09-30 21:48:22 +02:00
erikinkinen referenced this pull request from erix/docs2026-09-30 21:48:23 +02:00
erikinkinen referenced this pull request from erix/e2fsd2026-09-30 21:48:27 +02:00
erikinkinen referenced this pull request from erix/fatd2026-09-30 21:48:27 +02:00
erikinkinen referenced this pull request from erix/integration2026-09-30 21:48:28 +02:00
erikinkinen referenced this pull request from erix/rootd2026-09-30 21:48:29 +02:00
WIP: Align signed runtime dependenciesto WIP: Define original-device durability and undo journalingThe block-device client now pins LibIPC
61b43723in 9b335e80. This is part of the Vfsd dependency repair; the existing interfaces are unchanged, and Integration consumer adoption is in progress.Replaced by #4, #5. These feature branches preserve the original source in separate changes. Closing this combined PR without merging it; the original branch is retained.
Pull request closed