[BUG] Counted mediator startup mapping does not preserve its read-only contract #6
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/procd#6
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 first published private provisioning producer used the writable packet-workspace mapping rights for the separate counted startup page as well. The startup contract requires that page to remain read-only to the child. The correction is already published in Procd d04311abff67; this report retains the defect and validation boundary.
Reproduction
At
1eb81302d0e14c4562ba776fb563f215b5a9cc6f, strengthenproducer_provision_maps_counted_workspace_and_retires_probe_before_setupto require READ|MAP for the first mapped page and READ|WRITE|MAP for each following workspace page, then runcargo test --locked --offline --bin procd producer_provision_maps_counted_workspace_and_retires_probe_before_setup. The retained original run fails its first-page rights assertion: actual 11, expected 9; one test failed with status 101.Expected and actual behavior
Expected: a child-readable, non-writable, non-executable startup page and a separate writable/non-executable packet workspace. The held Process route may populate startup backing before execution without granting child WRITE. Actual: the producer requested the workspace rights for all pages. The corrected implementation distinguishes the first startup page before native MAP_FRAME, while preserving frame alias disposal, the original controller route and subsequent startup/lifetime ordering.
Environment and identity
1eb81302d0e14c4562ba776fb563f215b5a9cc6f; correctiond04311abff67e7355bd92bb2e48fb6161e0ec674.Evidence and prior checks
The strengthened test fails before the correction and passes after it. All four strict configurations pass 327 default/333 all-feature main tests plus five probes, nine native build profiles, thirteen strict Clippy selections and private rustdoc with zero warnings. Formatting, Markdown and dependency checks pass. The original failed assertion and documentation wrapping corrections remain retained. Kernel's existing startup control test demonstrates controller population of a READ|MAP child mapping; actual Posixd guest execution remains a distinct requirement. Original publication CI is being monitored separately.
Tracking
Startup protection regression 6 remains open for actual guest acceptance.
Related: Procd authority work, implementation PR, native startup, and Phase 6 completion. Keep current guest acceptance and publication CI open; the signed fix and its failing-before/passing-after regression are available for review.
erikinkinen referenced this issue2026-09-24 18:54:01 +02:00
erikinkinen referenced this issue from erix/integration2026-09-24 19:07:21 +02:00