[BUG] Realm provider endpoints lack owned-invocation intake #100

Closed
opened 2026-09-29 11:36:02 +02:00 by erikinkinen · 0 comments
Owner

Summary

Implemented in the signed source graph below. The affected revisions lacked original owned receiver registration and serving on stream/exact providers, so native mediator operations and cleanup could not reach them. Both producer paths are now connected.

Launchd registers original realm stream receivers before exporting SEND views and serves actual owned CLAIM/COMPLETE/RELINQUISH. Each noncopyable row retains its exact Reply result. Vfsd registers exact endpoints before Powerbox, Launchd and cwd export, preserves legacy users and reserves original delivery storage independently of copied handle metadata. Every allocation family respects that reservation through provider Close and native/receiver settlement. Neither path replays an operation or COMPLETE after refusal. Native route invalidation retains draining custody until acknowledgment; request abandonment preserves an open stream and explicit Close preserves the lender.

Compiler-derived rows account for full protocol packets; Vfsd capacity descriptor version two includes mount, handle and invocation regions. Cleanup scrubs only written packet extents, conservatively retaining the full extent for unknown native output. This is a source cost reduction, not a measured performance result. Eight Launchd, nine Vfsd and four packaging controls are authored but unrun; existing arena controls are updated. The existing native binding workload exercises external writes, Close, exact process exits and lender preservation under unchanged gates.

Inline/component/manual contracts and coherent catalog adoption are updated. Changed code files remain below 1,000 lines (maximum 957); missing_docs enforcement remains and Rust formatting was applied. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction. No execution pass or warning-free build is claimed. The transport defect and stream feature are implemented; native filesystem permission policy, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.

Phase completion is 16.21% weighted, 4.81% whole-item, with 20/460 parents and 434/894 sub-items complete. Binding cleanup acceptance is restored for completed implementation; waived testing is not a test pass.

Reproduction

Original source-level reproduction against the affected revisions; no VM or test was run. Follow Posixd authority retirement SUBMIT to Kernel invocation admission, which requires an original live owned receiver registration. Compare Launchd's stream receiver priming/legacy stream scheduler and Vfsd's exact-directory legacy dispatcher. Neither path registers or claims these owned calls. A received SEND endpoint alone cannot meet the registration condition; admission returns NOT_FOUND before a normal provider call exists. The authored realm-binding scenario reaches these paths during operation and teardown.

Expected and actual behavior

Expected: original provider endpoints register before export, admit cap-free owned calls with retained serving/result custody, preserve fair cancellation and reply-before-receiver-disposal ordering, and return exactly the envelope the consumer correlates. Existing legacy users retain their explicit contract where required.

Affected source behavior: owned SUBMIT requires registration, while these providers expose only legacy receive/reply. There is no automatic bridge. Legacy envelopes also use CALL framing, while the owned consumer requires REPLY; native owned completion treats payload bytes as opaque. Do not weaken correlation or invent successful retirement to mask the missing producer implementation.

Environment and identity

  • Consumer: Posixd 40fbf556, src/realm_authority/retirement.rs; the inherited-I/O consumer is under implementation in the stream feature.
  • Stream provider: Launchd 2d403bfe, src/runtime/stream_service.rs, src/realm_stream_source.rs and src/syscall_peer/private_receiver.rs.
  • Directory provider: Vfsd 3ba2ee6a, src/runtime/exact.rs.
  • Integration source graph: 2842f5d5; native binding fixture on x86-64.
  • Image digest/runtime execution: unavailable for this finding; tests/builds/CI observation are deferred by instruction.
  • Authority: only the originally received per-client provider SEND and exact provider receiver.
  • Last known working revision: none established for this cross-transport path.

Evidence and prior checks

Kernel src/kobj/endpoint/invocation/admission.rs selects table::receiver(endpoint) and refuses missing live registration before request admission. Native owned and legacy endpoint dispatch are distinct. Source inspection is evidence of the missing adapter, not a passing or failed VM result. Existing host fixtures model compatible providers and therefore do not establish this native connection.

Tracking

Implemented by Launchd, Vfsd, Integration and the manual, with the stream consumer. Native binding cleanup acceptance is restored for completed code. Phase tracking retains the remaining filesystem permission work and guest rebuilds. Test execution remains waived, without a pass claim.

Producer implementation design

Register each original recipient stream receiver before exporting its SEND view, with zero capability inputs and the complete existing stream payload ceiling. Serve actual owned CLAIM/COMPLETE/RELINQUISH on that receiver; produce the owned Reply envelope explicitly while retaining the legacy CALL envelope for legacy routes. Keep one noncopyable delivery and its exact response in counted provider storage. A completion refusal retains that result and permits only original invalidation/retirement, never replay. Dropping the receiver during realm teardown must also settle the original delivery before its storage or generation can be reused. Request cancellation alone preserves an open view; explicit Close retires the backend before acknowledgement and the receiver after the reply boundary.

Apply the same original-receiver and result-retention rules to Vfsd exact endpoints, preserving their operation ceilings and legacy users. A provider record must remain reserved while its owned reply or retirement remains outstanding. Native provider registration is a prerequisite to export, not a lazy effect after the recipient can submit. No new discovery path, caller-selected owner, capability input, fallback authority or global result bottleneck is introduced. Existing protocol widths and compiler-derived counted storage determine capacity.

Author positive, malformed-input, refused-completion, cancellation, close and teardown controls. Testing, builds and CI observation remain deferred at the user's request; implementation status will be reported separately for both producers.

## Summary Implemented in the signed source graph below. The affected revisions lacked original owned receiver registration and serving on stream/exact providers, so native mediator operations and cleanup could not reach them. Both producer paths are now connected. Launchd registers original realm stream receivers before exporting SEND views and serves actual owned CLAIM/COMPLETE/RELINQUISH. Each noncopyable row retains its exact Reply result. Vfsd registers exact endpoints before Powerbox, Launchd and cwd export, preserves legacy users and reserves original delivery storage independently of copied handle metadata. Every allocation family respects that reservation through provider Close and native/receiver settlement. Neither path replays an operation or COMPLETE after refusal. Native route invalidation retains draining custody until acknowledgment; request abandonment preserves an open stream and explicit Close preserves the lender. Compiler-derived rows account for full protocol packets; Vfsd capacity descriptor version two includes mount, handle and invocation regions. Cleanup scrubs only written packet extents, conservatively retaining the full extent for unknown native output. This is a source cost reduction, not a measured performance result. Eight Launchd, nine Vfsd and four packaging controls are authored but unrun; existing arena controls are updated. The existing native binding workload exercises external writes, Close, exact process exits and lender preservation under unchanged gates. Inline/component/manual contracts and coherent catalog adoption are updated. Changed code files remain below 1,000 lines (maximum 957); missing_docs enforcement remains and Rust formatting was applied. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction. No execution pass or warning-free build is claimed. The [transport defect](https://git.erikinkinen.fi/erix/integration/issues/100) and [stream feature](https://git.erikinkinen.fi/erix/posixd/issues/11) are implemented; [native filesystem permission policy](https://git.erikinkinen.fi/erix/posixd/issues/10), both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) is **16.21% weighted**, **4.81% whole-item**, with **20/460 parents** and **434/894 sub-items** complete. Binding cleanup acceptance is restored for completed implementation; waived testing is not a test pass. ## Reproduction Original source-level reproduction against the affected revisions; no VM or test was run. Follow Posixd authority retirement SUBMIT to Kernel invocation admission, which requires an original live owned receiver registration. Compare Launchd's stream receiver priming/legacy stream scheduler and Vfsd's exact-directory legacy dispatcher. Neither path registers or claims these owned calls. A received SEND endpoint alone cannot meet the registration condition; admission returns NOT_FOUND before a normal provider call exists. The authored realm-binding scenario reaches these paths during operation and teardown. ## Expected and actual behavior Expected: original provider endpoints register before export, admit cap-free owned calls with retained serving/result custody, preserve fair cancellation and reply-before-receiver-disposal ordering, and return exactly the envelope the consumer correlates. Existing legacy users retain their explicit contract where required. Affected source behavior: owned SUBMIT requires registration, while these providers expose only legacy receive/reply. There is no automatic bridge. Legacy envelopes also use CALL framing, while the owned consumer requires REPLY; native owned completion treats payload bytes as opaque. Do not weaken correlation or invent successful retirement to mask the missing producer implementation. ## Environment and identity - Consumer: [Posixd 40fbf556](https://git.erikinkinen.fi/erix/posixd/commit/40fbf556a0fb8fbf719101c1670957dbcced25d3), `src/realm_authority/retirement.rs`; the inherited-I/O consumer is under implementation in [the stream feature](https://git.erikinkinen.fi/erix/posixd/issues/11). - Stream provider: [Launchd 2d403bfe](https://git.erikinkinen.fi/erix/launchd/commit/2d403bfe9ade76fecfb33ff9b5bfa2657f34bde5), `src/runtime/stream_service.rs`, `src/realm_stream_source.rs` and `src/syscall_peer/private_receiver.rs`. - Directory provider: [Vfsd 3ba2ee6a](https://git.erikinkinen.fi/erix/vfsd/commit/3ba2ee6a75ecc33494f744521d61328974f8c870), `src/runtime/exact.rs`. - Integration source graph: [2842f5d5](https://git.erikinkinen.fi/erix/integration/commit/2842f5d54a83a0794f4b085a345eb358a9ec353a); native binding fixture on x86-64. - Image digest/runtime execution: unavailable for this finding; tests/builds/CI observation are deferred by instruction. - Authority: only the originally received per-client provider SEND and exact provider receiver. - Last known working revision: none established for this cross-transport path. ## Evidence and prior checks Kernel `src/kobj/endpoint/invocation/admission.rs` selects `table::receiver(endpoint)` and refuses missing live registration before request admission. Native owned and legacy endpoint dispatch are distinct. Source inspection is evidence of the missing adapter, not a passing or failed VM result. Existing host fixtures model compatible providers and therefore do not establish this native connection. ## Tracking Implemented by [Launchd](https://git.erikinkinen.fi/erix/launchd/pulls/2), [Vfsd](https://git.erikinkinen.fi/erix/vfsd/pulls/3), [Integration](https://git.erikinkinen.fi/erix/integration/pulls/12) and the [manual](https://git.erikinkinen.fi/erix/docs/pulls/4), with the [stream consumer](https://git.erikinkinen.fi/erix/posixd/pulls/5). Native binding cleanup acceptance is restored for completed code. [Phase tracking](https://git.erikinkinen.fi/erix/integration/issues/65) retains the remaining filesystem permission work and guest rebuilds. Test execution remains waived, without a pass claim. ## Producer implementation design Register each original recipient stream receiver before exporting its SEND view, with zero capability inputs and the complete existing stream payload ceiling. Serve actual owned CLAIM/COMPLETE/RELINQUISH on that receiver; produce the owned Reply envelope explicitly while retaining the legacy CALL envelope for legacy routes. Keep one noncopyable delivery and its exact response in counted provider storage. A completion refusal retains that result and permits only original invalidation/retirement, never replay. Dropping the receiver during realm teardown must also settle the original delivery before its storage or generation can be reused. Request cancellation alone preserves an open view; explicit Close retires the backend before acknowledgement and the receiver after the reply boundary. Apply the same original-receiver and result-retention rules to Vfsd exact endpoints, preserving their operation ceilings and legacy users. A provider record must remain reserved while its owned reply or retirement remains outstanding. Native provider registration is a prerequisite to export, not a lazy effect after the recipient can submit. No new discovery path, caller-selected owner, capability input, fallback authority or global result bottleneck is introduced. Existing protocol widths and compiler-derived counted storage determine capacity. Author positive, malformed-input, refused-completion, cancellation, close and teardown controls. Testing, builds and CI observation remain deferred at the user's request; implementation status will be reported separately for both producers.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:17 +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/integration#100
No description provided.