[BUG] Counted mediator startup mapping does not preserve its read-only contract #6

Open
opened 2026-09-24 18:40:30 +02:00 by erikinkinen · 0 comments
Owner

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, strengthen producer_provision_maps_counted_workspace_and_retires_probe_before_setup to require READ|MAP for the first mapped page and READ|WRITE|MAP for each following workspace page, then run cargo 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

  • Component: Procd feature branch, original producer 1eb81302d0e14c4562ba776fb563f215b5a9cc6f; correction d04311abff67e7355bd92bb2e48fb6161e0ec674.
  • Build: strict hosted producer effect test plus native build matrices on the original immutable shared graph.
  • Platform/toolchain: Linux x86-64, Rust 1.97.1; guest startup acceptance is pending.
  • Authority: original Procd Process control and retained frame custody; the fix adds no route or capability.
  • Last known working producer: no earlier accepted native provisioning witness.

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.

## 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](https://git.erikinkinen.fi/erix/procd/commit/d04311abff67e7355bd92bb2e48fb6161e0ec674); this report retains the defect and validation boundary. ## Reproduction At `1eb81302d0e14c4562ba776fb563f215b5a9cc6f`, strengthen `producer_provision_maps_counted_workspace_and_retires_probe_before_setup` to require READ|MAP for the first mapped page and READ|WRITE|MAP for each following workspace page, then run `cargo 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 - Component: Procd feature branch, original producer `1eb81302d0e14c4562ba776fb563f215b5a9cc6f`; correction `d04311abff67e7355bd92bb2e48fb6161e0ec674`. - Build: strict hosted producer effect test plus native build matrices on the original immutable shared graph. - Platform/toolchain: Linux x86-64, Rust 1.97.1; guest startup acceptance is pending. - Authority: original Procd Process control and retained frame custody; the fix adds no route or capability. - Last known working producer: no earlier accepted native provisioning witness. ## 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](https://git.erikinkinen.fi/erix/procd/issues/6) remains open for actual guest acceptance. Related: [Procd authority work](https://git.erikinkinen.fi/erix/procd/issues/1), [implementation PR](https://git.erikinkinen.fi/erix/procd/pulls/2), [native startup](https://git.erikinkinen.fi/erix/integration/issues/1), and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Keep current guest acceptance and publication CI open; the signed fix and its failing-before/passing-after regression are available for review.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:10 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/procd#6
No description provided.