WIP: Forward flush barriers through the selected block provider #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/blockd!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
Forward a flush request for a whole disk or GPT partition through its already selected backing provider. Partition metadata inherits flush support only from writable media; read-only and unsupported devices refuse the operation. Keep provider correlation, binding invalidation and cleanup intact, and never replay an accepted barrier.
Update the pinned runtime dependencies and CI helper, document the durability contract, and skip duplicate same-repository pull-request jobs.
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 held provider binding supplies the authority to flush the requested device. A partition resolves to its recorded parent device; numeric IDs do not acquire another route. The response retains the caller's original request and device correlation. Transport failures follow the existing provider invalidation and retirement rules.
The dependency updates use full commit hashes. The CI guard skips only same-repository pull requests; pushes, fork pull requests and manual runs retain their existing eligibility.
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/integration2026-09-21 19:41:59 +02:00
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: Forward flush barriers through the selected block providerReplaced by #4, #5, #6. These focused PRs retain the original durability implementation and its component contracts. Closing without merging; the original branch remains available.
Pull request closed