Control retained files through original recovery owners #46
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/e2fsd!46
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/ext-retained-file-controls"
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?
Resize and synchronize an acquired inode through its original mount and recovery owner. Resize uses one complete transaction, preserves real allocation failures and returns no implicit persistence guarantee. Sync flushes the selected journal and filesystem routes; uncertain completion permanently quarantines the provider.
Depends on #45 and IPC #113. The source profile selects the complete public crypto and undo-journal suppliers.
Native VFS/POSIX consumer wiring and release-image acceptance remain separate work.
WIP: Control retained files through original recovery ownersto Control retained files through original recovery ownersThe original-inode controls are ready for review with IPC #113. Resize updates every retained alias and zeroes newly exposed content. Both sync operations use the original recovery owner and block routes; loss of either barrier permanently quarantines the provider, including after reset.