[BUG] Empty configuration CLAIM aborts private realm startup #5
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#5
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 startup treats the Kernel's normal empty configuration-queue result as a permanent failure. Kernel CLAIM returns
NOT_FOUNDwith delivery owner zero when no invocation is queued; Launchd recognizes onlyRETRYwith owner zero as idle. It recordsNativeStatus(3), retires its retained owners, and can return a typed public START refusal.The changed-image native scenario reaches the actual Posixd PREPARE successfully, then receives
NOT_FOUNDfor START. The source defect matches that result. The guest does not emit an internal bootstrap-stage trace, so this report does not claim direct observation of the precise failing instruction.Reproduction
At Integration
fa857c0964774def6777142afeb7a3c16440abeeand Launchdeb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d, run the original selected native scenario:The smaller deterministic trigger is a registered, currently empty configuration receiver during Provision, Start or Ready. Return the actual native empty CLAIM pair
(IPC_RESULT_NOT_FOUND, 0)before the next ContextProbe/Ready delivery, including the normal interval after completing ContextProbe while the producer retires its caller. The original host fixture instead supplied only(IPC_RESULT_RETRY, 0)for idle intake.Expected and actual behavior
A zero-owner empty CLAIM must preserve the retained bootstrap and allow independent producer/configuration progress. Every nonzero returned delivery must remain owned even if its status is erroneous. Other failures must remain failures; no additional authority or wire change is needed.
The original native receipt contains:
Request
0x13, operation0x6D4(START), receives a valid typed rejection withNOT_FOUND(3). The startup marker is absent. Exsh's endpoint0x520exits0xE5; that status is not evidence of a Launchd process-event exit. Rootd later exits0xDC. The scenario returns 1, and its unchanged 45-second progress watchdog terminates QEMU. No native readiness or retirement acceptance is established.Environment and identity
fa857c0964774def6777142afeb7a3c16440abee; Launchdeb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d; Procdd04311abff67e7355bd92bb2e48fb6161e0ec674; Posixd809647d60544c4c6121868c99133f30d054965c9; Kernel5e285aa91a1423523b2a094d4ce0449ada39b16c.95c48dc71a5d7fd0f1282d33e68f86ed2997d5be529f518f50e53efa2d6baf0d. The runner uses a writable disk; this digest does not assert equality with preboot bytes.803bd99106573710f28ffb2d2a994f22c8d24fb29910447e5cc643c8ed498aef. Image construction recorded no warnings.Evidence and prior checks
Kernel queued lookup returns
NOT_FOUNDfor an empty registered queue. Server CLAIM propagates it; wire rejection returns a zero owner.Launchd configuration intake accepts only
RETRY/zero as idle. Bounded progress retains the failure and starts cleanup; the public result mapping preserves native status 3. Procd's existing owned receiver already treats zero-ownerRETRYorNOT_FOUNDas idle.The original failed run and complete serial evidence remain retained. No unchanged-image retry or timeout relaxation was used. The source correction and strict validation described below are complete. Changed-source native validation remains pending.
Signed correction cf6d4a70d5423dca65bbab5e8092fd374184c4ed treats only zero-owner
NOT_FOUNDorRETRYas idle. The native-faithful fixture now defaults toNOT_FOUND; regression controls cover both empty statuses and preserve erroneous nonzero owners. All 12 focused startup controls pass. The complete default, all-feature and runtime-feature development/release matrix passes 329 library and 67 runtime tests in each of six configurations, with formatting, strict host/native Clippy, warning-denied native builds, host/native rustdoc and documentation/dependency checks reporting zero warnings.Both original exact-head CI runs, 153 and 154, passed. Their complete Rust and Markdown logs were reviewed with no warning or failure candidates. Integration 8f9b7d752c4769e3017aa4116ad0a542f54f488b selects the signed correction. Actual changed-image startup, readiness and independent retirement remain pending; this issue remains open.
Tracking
Launchd lifecycle audit, Launchd PR 2, Posixd realm lifecycle, Integration validation, and Phase 6 completion. The previous private preparation defect is a separate failure now passed by this receipt; the WAIT decoder defect is not assigned as this START failure's cause.
NOT_FOUNDwith a regression control against the failing source, including normal empty intervals between bootstrap messages.NOT_FOUNDorRETRYas idle, preserving all nonzero handle custody and other errors.Baseline regression reproduced against unchanged production:
cargo test --locked --offline --all-targets empty_configuration_claims_preserve_private_start_progress -- --nocapturereturns 101 with one failing control. The native-faithful empty-queue result produces public START result 3 instead of successful progress. This is host reproduction evidence, not a corrected matrix or native acceptance. Original failure output and source identity remain retained.erikinkinen referenced this issue from erix/integration2026-09-24 20:11:14 +02:00