[FEATURE] Publish exact native outputs through retained provider owners #39
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/vfsd#39
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem and motivation
Native build tools need to publish complete output files atomically. An ordinary file writer does not own the parent entry or the adjacent temporary needed for replacement and failure cleanup.
Proposed behavior and scope
Vfsd acquires an exact output publisher through the authenticated invocation scope and carries it through a counted provider owner. Native operations use a distinct publication endpoint. Ramfsd and E2fsd supply their corresponding retained transactions; ordinary WRITE keeps its existing meaning.
Authority, security and reliability
Only an admitted invocation-scoped Publish operation can acquire this owner. Effective identity and the current creation mask come from the original authenticated launch; fresh parent policy determines creation metadata. Missing policy refuses acquisition.
Retain the original provider, mounted branch, parent, destination and temporary. Commit never resolves the pathname again. A later overlay cannot retarget the held underlying entry; original root revocation still fences ordinary effects. Preserve the first operation result, actual reply bytes and independent cleanup failures. Uncertain Commit permits only original Status settlement, without replay or replacement authority. Retire the provider owner before releasing surrounding pins or reusing its row.
Acceptance criteria
Alternatives and tradeoffs
Extending ordinary WRITE would conflate file-content rights with entry replacement. Keeping only a pathname would permit later resolution to select a different object. A global mount revision fence would also invalidate unrelated sibling changes; retaining the selected branch preserves existing held-object semantics.
Tracking and rollout
Coordinate Boot-tool #6, Launchd #26, Ramfsd #12, and E2fsd #25. Component changes are submitted through Vfsd PR #3. No legacy shorter acquisition shape or implicit creation identity is accepted.