[FEATURE] Publish exact native outputs through retained provider owners #39

Open
opened 2026-10-24 06:57:53 +02:00 by erikinkinen · 0 comments
Owner

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

  • Connect authenticated acquisition, complete creation metadata and counted owner storage to native dispatch.
  • Implement confirmed-prefix writes, persistence, writer close, one Commit, original Status and certain unpublished Abort.
  • Preserve denial, partial-effect, malformed-reply and independent cleanup observations; fence revoked original roots.
  • Cover replacement, mounted branches, later overlays, uncertain Commit and once-only retirement through the real resolver and provider interfaces.
  • Update component documentation and the technical manual, and adopt matching producer/provider revisions together.
  • Exercise the complete native build-tool workflow in the VM with original cleanup and exact output checks.

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.

## 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 - [ ] Connect authenticated acquisition, complete creation metadata and counted owner storage to native dispatch. - [ ] Implement confirmed-prefix writes, persistence, writer close, one Commit, original Status and certain unpublished Abort. - [ ] Preserve denial, partial-effect, malformed-reply and independent cleanup observations; fence revoked original roots. - [ ] Cover replacement, mounted branches, later overlays, uncertain Commit and once-only retirement through the real resolver and provider interfaces. - [ ] Update component documentation and the technical manual, and adopt matching producer/provider revisions together. - [ ] Exercise the complete native build-tool workflow in the VM with original cleanup and exact output checks. ## 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](https://git.erikinkinen.fi/erix/boot-tool/issues/6), [Launchd #26](https://git.erikinkinen.fi/erix/launchd/issues/26), [Ramfsd #12](https://git.erikinkinen.fi/erix/ramfsd/issues/12), and [E2fsd #25](https://git.erikinkinen.fi/erix/e2fsd/issues/25). Component changes are submitted through [Vfsd PR #3](https://git.erikinkinen.fi/erix/vfsd/pulls/3). No legacy shorter acquisition shape or implicit creation identity is accepted.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:20 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/vfsd#39
No description provided.