[BUG] Private realm preparation requires an ordinary launch manifest #4
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#4
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
Private realm preparation wrongly requires an ordinary executable launch manifest before selecting the realm-specific Loaderd path. The actual Posixd package deliberately has no ordinary launch sidecar or public launch row, so the first PREPARE for the actual mediator returns
NOT_FOUNDeven though the exact executable exists in the image. This prevents the native startup scenario from reaching Posixd startup or readiness.Reproduction
With Integration
ffedb3630895b2bc547ab58e4900f750d84cd64b, Launchd0bb56cc229fe4563da6c77ebe6ce9c178b903f26, Procdd04311abff67e7355bd92bb2e48fb6161e0ec674and the selected component graph, run:The original local native scenario reaches the existing admission/preparation markers, then attempts PREPARE for the actual Posixd executable. This failure has been observed once; no unchanged-input retry or deadline change was performed. The associated source path provides the smaller deterministic policy trigger: prepare a private realm executable with its valid exact source present and no ordinary
.lmfsidecar.Expected and actual behavior
Private realm preparation should resolve and authenticate the exact executable within the supplied scope, submit the realm-specific Loaderd request, and retain all original source and cleanup owners. It must not grant ordinary client authority or require an ordinary launch manifest for a private mediator. Ordinary executable preparation must continue enforcing its own manifest contract.
The selected native receipt reports:
Request
0x12, operation0x6D1(PREPARE), receives a valid typed rejected reply withNOT_FOUND(3); kind0x0Bdenotes application rejection, not transport loss. The recorded exit status0xE5is also used by Exsh. Its endpoint0x520differs from Launchd's bound endpoint0x280, so this receipt must not be attributed to a Launchd process-event exit. Rootd later exits0xDC, and the original 45-second progress watchdog terminates QEMU. The scenario returns 1 before the requiredREALM_STARTUP:VERIFIEDmarker; no actual mediator start, readiness or retirement is accepted.Environment and identity
ffedb3630895b2bc547ab58e4900f750d84cd64b; Launchd:0bb56cc229fe4563da6c77ebe6ce9c178b903f26; Procd:d04311abff67e7355bd92bb2e48fb6161e0ec674; Posixd:809647d60544c4c6121868c99133f30d054965c9.e9a66bf5887f1d0fdb746080e0b6b10e5bd7923b02c8e2306e0d0586acf937b0. Read-only image inspection leaves those bytes unchanged./bin/posixdand its packaged object-store executable refer to inode 51 and the same 264,000 bytes, SHA-256120e2f7e65f8ca8c4c1c72f7e1cf9deb9fb74428424b156f5a92afc76d976f23. The runtime graph identifies the Posixd executable; the image has no ordinary Posixd launch row or/bin/posixd.lmfsidecar.Evidence and prior checks
Read-only image inspection confirms that this is not a missing executable alias. Source inspection at the exact revision establishes the mismatched path:
RealmTablepreparation calls the commonProgramPreparation::resolve.ProgramPreparation::resolveunconditionally requests an ordinary manifest before selecting the private Loaderd operation. The manifest lookup appends.lmf; its absence becomesManifestRejectedwith the originalNOT_FOUND.The original 107-file evidence inventory and 56,013-byte serial log are retained. Serial SHA-256:
a1132d376e101c370f06f7522f45139d34703e8d385847e848f6d4f84c43ae72. Image construction has no recorded warnings; stderr preserves the expected watchdog failure. The image inspection and source correlation do not constitute a corrected VM pass. Earlier admission/preparation checks used other executable fixtures and do not establish actual Posixd readiness.Tracking
Native private-path acceptance — 25 September 2026: signed Launchd
3d39c7413a9c35a051323fceb7f895f0b18402e0in Integration66ddc78da31dd03dd554d0677cdc2af86588d525passes the maintained actual two-mediator startup witness. Exact/bin/posixdpreparation succeeds without an ordinary launch sidecar; both mediators reach PrivateReady, retire independently and reject stale handles under unchanged120/45-second limits. This closes the private-path defect; configuration, seal and four-client I/O remain separate acceptance work.The first START, request
0x13/ operation0x6d4, returns a typed NOT_FOUND rejection before the startup marker. No startup acceptance or checklist increase is awarded.Source review and fail-before controls identify empty registered-CLAIM handling defects in Launchd issue 5 and Posixd issue 7: Kernel empty intake returns NOT_FOUND with no delivery owner. A separate Procd first-challenge registration race can also reject an unaccepted call before the new child registers. The public START code alone does not distinguish internal failure locations. Corrections retain nonzero owners, exact origins and accepted-call ownership; the next native attempt must adopt the reviewed fixes together.
The independently reviewed explicit retirement event gap, linked to Launchd issue 6, must transfer only the exact terminal observation into the retained Retire acknowledgment after actual child/capability disposal. Spontaneous WAIT and other generations stay independently visible. It is not attributed as this START failure's cause. Configuration/seal, four real clients, byte I/O and all toolchain/EriX guest builds remain open.
Docs
95921234c64d7cc11f9f9ed19d49a5d73c95357cpublishes the preceding private preparation/event-contract correction: 45 tests and the full 2,497-page manual pass, all 464,159 word bounds pass and six affected pages were visually reviewed. Original Docs CI 1065/1066 passes with zero final warnings; intermediate TeX reference convergence remains recorded. Further intake/retirement contract prose is a separate pending change. Launchd's original 151/152 CI passes with four complete warning-free logs; Integration 1787/1788 awaits runner assignment. Weighted progress remains 15.16%.The same checkpoint fixes the independently reproduced WAIT decoder defect by accepting exactly ordinary-child and realm-mediator terminal roles before matching the retained process generation. Invalid identity, framing, state and authority remain rejected. All six default/all-feature/production development/release configurations pass 329 library and 66 runtime tests each, strict host/native Clippy, native builds, private rustdoc, formatting and documentation checks, with zero warnings. Authored Rust files remain below 1,000 lines. Final documentation corrections preserve the tested Rust behavior.
The original failed VM remains retained. A newly selected image must pass the unchanged actual startup/readiness/retirement scenario before native acceptance; configuration/seal, four clients, byte I/O and guest toolchain/EriX builds remain open. Private preparation issue 4 and independent event issue 3 remain distinct. WIP PR 2 and Phase 6 completion track the remaining acceptance.
Track the correction in Launchd PR 2, Launchd lifecycle audit, Integration validation and Phase 6 completion. The separate realm-event decoder defect is independently valid and is not assigned as this PREPARE failure's cause.
erikinkinen referenced this issue from erix/integration2026-09-24 19:31:27 +02:00
erikinkinen referenced this issue2026-09-24 19:41:09 +02:00
erikinkinen referenced this issue from erix/docs2026-09-24 20:00:34 +02:00