[BUG] Private Provision assumes an endpoint SEND source is moved #7
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/launchd#7
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?
Summary
Launchd treats the configuration SEND passed to private Provision as a moved capability, but native owned invocation copies ordinary endpoint bindings. After a successful Provision result and caller retirement, Launchd queries its original SEND source, finds the expected retained copy, and fails with
SourceAuthority. Public START then returns INTERNAL before native child Start.A bounded hardware-breakpoint diagnostic of the exact failing image identifies this boundary. The host transport fixture incorrectly removes the SEND source at SUBMIT and therefore misses the actual native behavior.
Reproduction
At Integration
8f9b7d752c4769e3017aa4116ad0a542f54f488band Launchdcf6d4a70d5423dca65bbab5e8092fd374184c4ed, run:The retained original execution completes admission and guarded preparation, then rejects request
0x13, operation0x6D4, with result5(INTERNAL). A separate changed-debugger execution of the unchanged image captures Launchd's first failure while retaining a successful private Provision reply (0x433, result zero, Provisioned). This diagnostic is not an acceptance run or a failure-frequency estimate.A deterministic host regression should preserve the ordinary configuration SEND source when SUBMIT succeeds, return the matching Provision acknowledgment and finish the original caller's retirement. The present implementation then fails its post-Provision source query. Unique InstallGrant and RevocationGrant transfers must continue using their existing MOVE behavior.
Expected and actual behavior
After validating Provision and retiring its original caller, Launchd must explicitly dispose of its own configuration SEND copy and independently prove that exact source slot absent before constructing native Start. The receiving child retains its intended SEND descendant; dropping a local copied binding must not be confused with revoking the descendant. Any disposal refusal, failed absence query or retained source must prevent Start and preserve cleanup ownership.
Instead,
advance_callcallsverify_column(2)without a preceding local drop because it assumes native transfer consumed the source. The actual query succeeds, producingSourceAuthority; the public mapper returns INTERNAL. The exact diagnostic capture is still in phase Provision with no previous failure, a valid 224-byte Provision reply, and the original configuration source marked owned. No native Start, Posixd readiness or running retirement is established.Environment and identity
8f9b7d752c4769e3017aa4116ad0a542f54f488b; Launchdcf6d4a70d5423dca65bbab5e8092fd374184c4ed; Procd4f3b01bf21932e86ac542f07e6ade05138cc0473; Kernel5e285aa91a1423523b2a094d4ce0449ada39b16c; Posixd5f54a55a5f189559352c7d0e6a2af55aaa37c44f.396e15c2ba4f81bf2d39a86eb11d6b536588b32ad671c02a724ced602906c65b. Both the retained original and diagnostic copy remain unchanged after diagnosis.66ddc78da31dd03dd554d0677cdc2af86588d525.Evidence and prior checks
The maintained
appliance-disk-image-realm-startup-positivescenario passes unchanged: both actual Posixd processes reach authenticated PrivateReady; A retires while B stays ready; B then retires; both stale handles are rejected; the initial shell exits successfully. The original required, unique, ordered and forbidden markers, expected guest exit0x10, 120-second guest hard limit and 45-second serial-progress limit all pass.This exercises counted minimum startup, actual capability census, setup-grant consumption and copied SEND disposal before Start, followed by native child registration, exact-origin readiness and the controller challenge. The packaged Posixd alias selects the same authenticated executable; no ordinary sidecar, extra child endpoint or fallback is introduced. Source-bound exercised gates are the evidence; no separate global inventory dump is claimed. Posixd's Ready caller remains its separately owned obligation until retirement. The successful explicit-retirement path does not exercise Launchd's spontaneous WAIT decoder, final CPU/profiler handoff, repeated row reuse, loss paths or capacity exhaustion.
Launchd's six strict local configurations pass 329 library and 69 runtime tests each; all 48 required commands are warning-free. The corrected native-faithful 14-test group includes COPY source retention, post-Provision caller retirement, separate source disposal/absence verification and failure preservation. Original Launchd CI155/156 also passes: four complete logs, 148,673 bytes, zero warning/failure candidates. Original Integration CI1791/1792 remains queued; earlier failures and regression reports remain preserved. The copied-SEND defect and its native startup regression are resolved at this scoped boundary. Relevant implementation reviews remain Launchd PR2, Procd PR2, Posixd PR5 and Integration PR12.
Configuration/seal/publication, four real clients and mediated byte I/O, complete running retirement and profiler disposition, rebuilding the external Rust/LLVM toolchain inside EriX and both complete EriX guest builds remain required and unproved. The WIP reviews remain unfinished.
Native Start is constructed only after explicit local SEND disposal and independent absence proof.
The native-faithful
copied_configuration_source_retires_after_provision_before_startcontrol fails against unchanged productioncf6d4a70d5423dca65bbab5e8092fd374184c4edwithSome(SourceAuthority)versusNone, exit 101. The corrected 14-test focused group passes, including source retention through Provision/RELEASE, separate disposal/query turns and both disposal/query failures. The original failing control and its source identity remain retained.All six default/all-feature/runtime-feature development and release selections pass 329 library plus 69 runtime tests each. Formatting, strict host/native Clippy, native builds, warning-denied host/native rustdoc, doctests, dependency and Markdown checks complete with zero warnings. These checks cover the frozen published source. Original CI is monitored separately; no current CI success is inferred here. The subsequent changed-image startup/readiness/independent-retirement acceptance above closes this scoped bug.
Launchd's post-Provision check assumes a successful MOVE consumed its original SEND. The independent local query returns
SourceAuthoritywhen that slot still contains a capability. The host fixture instead deletes the source during SUBMIT.Kernel owned invocation admission uses the native transfer transaction: InstallGrant and RevocationGrant move, while endpoint bindings use
copy_cap_between_with_rights. The source remaining present is correct Kernel behavior.The diagnostic uses hardware breakpoints and a private host Unix socket. Symbol carriers preserve all packaged PT_LOAD bytes and geometry; the running executable-load bytes are also checked against the packaged ELF. The first
RetainedRealmStart::failentry has prior failure None, Provision phase, andSourceAuthority. Exact selected disassembly independently confirms the phase offset and that this error is produced by a successful capability query. The retained reply proves Provision completion arrived; an unhit optimized Procd completion symbol is not evidence that completion failed.The original acceptance attempt remains failed: command exit 1 after 169.570989 seconds including image construction, 107 retained artifacts, 56,013 serial bytes, zero image-warning candidates and no process-cleanup failure. The diagnostic also ends at the original progress watchdog, exit 1 after 95.831832 seconds. Its GDB index-cache warning and repeated-SIGTERM wrapper traceback are retained as host diagnostic issues; QEMU and GDB are both reaped, and no cleanup error remains. They do not alter the captured first guest failure or count as warning-free diagnostic execution. No raw guest memory or private environment is published.
Tracking
Integration's original INTERNAL failure, Launchd lifecycle audit, Launchd PR 2, Integration PR 12, and Phase 6 completion.
erikinkinen referenced this issue from erix/lib-ipc2026-09-24 20:57:29 +02:00
erikinkinen referenced this issue2026-09-24 21:10:16 +02:00
erikinkinen referenced this issue from erix/procd2026-09-24 21:10:19 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-24 21:10:21 +02:00
erikinkinen referenced this issue from erix/integration2026-09-24 21:10:26 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-24 21:35:28 +02:00