Update public source fixtures for descriptor-aware configuration framing #13
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#13
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
Resolved: public source fixtures now encode all nine capacity words, use the current 224-byte result budget and allocate 320 bytes for one client/two authority rows. Capacity-refusal literals also use the current frame, preserving their intended assertions. The new singleton scope fixture budgets 256 plan bytes. Tests are authored and unrun.
Several public realm source fixtures still encode the configuration frame and plan capacity from before descriptor-aware admission. They therefore cannot reach the source preparation, handoff and teardown paths they are intended to cover.
Reproduction
Source-derived, unexecuted reproduction: inspect the shared directory-source fixture and its stream/resize/handoff consumers. The literal BeginRealmConfiguration request emits eight capacity words after the realm handle, omitting the ninth file-descriptor word. It selects a 216-byte result budget while the current minimum is 224. Two-authority fixtures allocate 312 plan bytes although the current 120-byte header, one 72-byte client and two 64-byte authority records require 320.
Expected and actual behavior
Expected: complete current framing and explicit counted descriptor/storage budgets allow the fixture to reach its intended source operation and refusal/cleanup assertions.
Actual by source inspection: framing or capacity admission refuses before those paths. No executed test failure, build failure or CI outcome is claimed.
Environment and identity
44bc00753859a7129f5b1b0e059c8ebb6d0d0a89with the coordinated descriptor-aware configuration ABI.Evidence and prior checks
Native acquisition-scope preparation is implemented and published: lib-ipc
ab4e18f6, vfsdacc9a53a, launchd53ff53ca, posixd45976b69, exsh5308ec15, integration42f7d97b, docsfe1cd7d7.A distinct counted authority role connects public Launchd preparation, strict native scope transfer, VFS independent root/cwd ownership and sealed-client authority retirement. Root/cwd come from one actual held directory or live acquisition scope; preparation reopens no pathname and cannot widen its write ceiling. Every observation, acquisition and cleanup correlation is reserved before provider effects. Original source row, full generation, session and realm remain retained across lost replies, partial COPY and receiver disposal. Retirement disables new use before live children can delay disposal, while original child cleanup remains available. The generic broker mask and existing metadata/resize operations remain unchanged.
The native binding workload now prepares one read-only acquisition scope per client, with twenty authority rows and a 1684-byte plan per realm. Original provider and capability storage are explicitly budgeted. Twenty new controls are authored and unrun: four shared-wire, eleven VFS ownership/intake and five Launchd source/public-lifecycle cases. Existing Posixd authority, Exsh transcript and Integration geometry controls are extended. Provider correlation/cleanup and descriptor-aware source fixtures are resolved by implementation; no executed test failure or pass is claimed.
Full realm open/openat remains unfinished: native component dispatch, per-component/final permission mediation, raw path traversal, creation/append and Posixd descriptor serving still require implementation. Completion remains 16.91% weighted, 21/460 parents and 441/902 sub-items; this prerequisite adds no full-item acceptance. Tests, builds, lint checks, documentation generation, VM/profiler execution and CI observation remain deferred by instruction. Both full EriX guest-build generations and the Rust/LLVM guest rebuild remain unfinished.
Earlier evidence (historical; superseded where the current checkpoint above advances it):
The current shared wire defines a 96-byte configuration request, a 120-byte plan header and a minimum 224-byte result budget. Compare these with the literal fixture in
runtime/realm_directory_tests.rs, 312-byte source plan allocations and the handoff start request. Two unrelated capacity-refusal literals also retain the older frame width and must include the descriptor budget to exercise their intended refusal.Migrate the literal frames and explicit storage calculations while preserving original success, refusal, source ownership and cleanup expectations. New acquisition-scope coverage must use the current complete frame. Tests remain authored and unrun.
Tracking
Related Launchd implementation PR, realm open/openat and Phase 6 master issue.
erikinkinen referenced this issue from erix/blockd2026-09-29 21:46:03 +02:00
erikinkinen referenced this issue from erix/coreutils2026-09-29 21:46:26 +02:00
erikinkinen referenced this issue from erix/crashd2026-09-29 21:47:06 +02:00
erikinkinen referenced this issue from erix/deviced2026-09-29 21:47:28 +02:00
erikinkinen referenced this issue from erix/docs2026-09-29 21:47:56 +02:00
erikinkinen referenced this issue from erix/drv-acpi2026-09-29 21:48:24 +02:00
erikinkinen referenced this issue from erix/drv-i80422026-09-29 21:49:04 +02:00
erikinkinen referenced this issue from erix/drv-ps2-keyboard2026-09-29 21:49:21 +02:00
erikinkinen referenced this issue from erix/drv-ps2-mouse2026-09-29 21:50:53 +02:00
erikinkinen referenced this issue from erix/drv-rtc-cmos2026-09-29 21:50:53 +02:00
erikinkinen referenced this issue from erix/drv-serial2026-09-29 21:50:54 +02:00
erikinkinen referenced this issue from erix/drv-virtio-block2026-09-29 21:50:54 +02:00
erikinkinen referenced this issue from erix/dynlinkd2026-09-29 21:50:55 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-09-29 21:50:56 +02:00
erikinkinen referenced this issue from erix/exsh2026-09-29 21:50:57 +02:00
erikinkinen referenced this issue from erix/extop2026-09-29 21:50:58 +02:00
erikinkinen referenced this issue from erix/fatd2026-09-29 21:50:59 +02:00
erikinkinen referenced this issue from erix/fbcond2026-09-29 21:51:00 +02:00
erikinkinen referenced this issue from erix/hotplugd2026-09-29 21:51:01 +02:00
erikinkinen referenced this issue from erix/inputd2026-09-29 21:51:02 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 21:51:04 +02:00
erikinkinen referenced this issue from erix/irqd2026-09-29 21:51:05 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-29 21:51:06 +02:00
erikinkinen referenced this issue from erix/keyd2026-09-29 21:51:07 +02:00
erikinkinen referenced this issue2026-09-29 21:51:08 +02:00
erikinkinen referenced this issue from erix/lib-block2026-09-29 21:51:09 +02:00
erikinkinen referenced this issue from erix/lib-bootstrap2026-09-29 21:51:10 +02:00
erikinkinen referenced this issue from erix/lib-capabi2026-09-29 21:51:10 +02:00
erikinkinen referenced this issue from erix/lib-driver2026-09-29 21:51:11 +02:00
erikinkinen referenced this issue from erix/lib-input2026-09-29 21:51:12 +02:00
erikinkinen referenced this issue from erix/lib-interrupt2026-09-29 21:51:13 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-29 21:51:14 +02:00
erikinkinen referenced this issue from erix/lib-log2026-09-29 21:51:15 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-29 21:51:16 +02:00
erikinkinen referenced this issue from erix/lib-service2026-09-29 21:51:17 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-09-29 21:51:18 +02:00
erikinkinen referenced this issue from erix/lib-time2026-09-29 21:51:19 +02:00
erikinkinen referenced this issue from erix/lib-tty2026-09-29 21:51:19 +02:00
erikinkinen referenced this issue from erix/lib-vfs2026-09-29 21:51:20 +02:00
erikinkinen referenced this issue from erix/loaderd2026-09-29 21:51:21 +02:00
erikinkinen referenced this issue from erix/logd2026-09-29 21:51:22 +02:00
erikinkinen referenced this issue from erix/memd2026-09-29 21:51:23 +02:00
erikinkinen referenced this issue from erix/named2026-09-29 21:51:24 +02:00
erikinkinen referenced this issue from erix/pagerd2026-09-29 21:51:24 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-29 21:51:25 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-09-29 21:51:26 +02:00
erikinkinen referenced this issue from erix/probed2026-09-29 21:51:27 +02:00
erikinkinen referenced this issue from erix/procd2026-09-29 21:51:27 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-09-29 21:51:28 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-29 21:51:28 +02:00
erikinkinen referenced this issue from erix/seriald2026-09-29 21:51:29 +02:00
erikinkinen referenced this issue from erix/timed2026-09-29 21:51:30 +02:00
erikinkinen referenced this issue from erix/ttyd2026-09-29 21:51:30 +02:00
erikinkinen referenced this issue from erix/vfsd2026-09-29 21:51:31 +02:00
erikinkinen referenced this issue from erix/vspaced2026-09-29 21:51:32 +02:00