[BUG] Process-event decoder rejects valid realm mediator terminal replies #3
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#3
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
The authenticated process-event decoder admits only ordinary
LaunchChildterminal replies even though the runtime dispatcher also ownsRealmMediatorchildren. A valid realm-mediator terminal reply is rejected before it reaches that dispatcher.Correction to the initial report: the observed VM exit
0xE5does not identify Launchd or establish that this decoder defect caused the startup failure. Exsh uses the same exit status. The recorded exit endpoint is0x520, whereas Launchd is bound to0x280; these are different processes. The actual startup failure remains unresolved and no Posixd startup or readiness is accepted.Reproduction
The source-bound decoder trigger is a successful, correctly correlated WAIT_PROCESS_EVENT reply with a nonzero process identity and generation, a valid terminal state/event pair, zero flags/receipts, and the
RealmMediatorrole. At the selected Launchd revision, the explicit role check rejects it. This is an independently identified decoder defect; a regression test and correction are in progress.The associated native VM observation used Integration
ffedb3630895b2bc547ab58e4900f750d84cd64band its selected component graph, including Launchd0bb56cc229fe4563da6c77ebe6ce9c178b903f26and Procdd04311abff67e7355bd92bb2e48fb6161e0ec674, then run the maintained scenario:This is one original local native VM observation, not a successful CI receipt or an unchanged-input retry. The original 120-second scenario deadline and 45-second progress watchdog were retained. Failure frequency and a last known working revision are unestablished.
Expected and actual behavior
Launchd should process authenticated terminal events for its original ordinary-child and realm-mediator owners, then remain available for the actual private startup sequence. The scenario requires two actual Posixd mediators, authenticated readiness, independent retirement, stale-handle rejection and successful shell exit.
The serial receipt instead records, in order:
The recorded TCB
0x22exits through endpoint0x520, which differs from Launchd's bound endpoint0x280. Both Launchd and Exsh define an0xE5failure status, so that value alone does not establish which process exited or identify a Launchd process-event failure. Exsh's diagnostickind=0x0Bmeans a valid typed rejected reply, not transport loss: its first PREPARE for the actual Posixd sequence, request0x12/ operation0x6D1, returnsNOT_FOUND(3). Rootd then exits0xDC. The 45-second progress watchdog terminates QEMU after progress stops; the scenario command returns 1. The requiredREALM_STARTUP:VERIFIEDmarker is absent. That watchdog failure is preserved as a failed run, not a warning-free success.Environment and identity
ffedb3630895b2bc547ab58e4900f750d84cd64b; Launchd:0bb56cc229fe4563da6c77ebe6ce9c178b903f26; Procd:d04311abff67e7355bd92bb2e48fb6161e0ec674.5e285aa91a1423523b2a094d4ce0449ada39b16c; Rootd:2f1c7256eb77b6b29f1dad7d9b5028fdf8a7e527; Exsh:2239d5faabc0a52091af921484bee6bb2d558c0b; Posixd:809647d60544c4c6121868c99133f30d054965c9.a787946077c918e9426a8eac741afe2d4e51372a. It is distinct from the selected scenario driver above.e9a66bf5887f1d0fdb746080e0b6b10e5bd7923b02c8e2306e0d0586acf937b0. The writable post-VM disk is retained separately; no byte-identity inference substitutes for runtime acceptance.Evidence and prior checks
The retained evidence inventory covers 107 files. The complete serial log is 56,013 bytes, SHA-256
a1132d376e101c370f06f7522f45139d34703e8d385847e848f6d4f84c43ae72; its hash and length verify. Image construction has no recorded warnings. QEMU stderr retains the original progress-watchdog termination. Existing admission/preparation markers only prove those preceding checks; they do not establish actual Posixd startup, readiness or retirement.Source inspection identifies a concrete contract gap:
validate_procd_wait_process_event_replyadmits only theLaunchChildrole. The runtime dispatcher already checks realm ownership before ordinary jobs, but a validRealmMediatorevent cannot reach it through that decoder. This source-level defect is independent of the VM exit attribution. The serial log does not expose a rejected WAIT_PROCESS_EVENT reply and does not prove that the decoder branch caused the PREPARE rejection. The selected Exsh runtime also defines0xE5; its realm diagnostic encodes typed rejection as kind 11. Source-bound decoder regression tests and separate diagnosis of the native PREPARE failure remain required.Tracking
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 authority and lifecycle audit, Integration validation and Phase 6 completion.
[BUG] Launchd exits while decoding realm mediator terminal events during native startupto [BUG] Process-event decoder rejects valid realm mediator terminal replieserikinkinen 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