[BUG] Realm witnesses retain undersized canonical plan and stale reply budgets #103

Closed
opened 2026-10-12 11:03:35 +02:00 by erikinkinen · 0 comments
Owner

Summary

Realm witnesses retain undersized canonical plan and stale reply budgets. This prevents the original source witness from reaching its intended admission boundary.

Reproduction

Inspect runtime.realm-clients.vm.toml and runtime.realm-owner-loss.vm.toml (realm_plan_bytes=968), plus the bindings/FAT/exFAT configurations (3752), against their selected canonical header/client/group counts. Before this migration, header144/client72 already require two 492-byte client plans (984 total), and two 1900-byte binding plans (3800 total). Also inspect the selected Posixd non-pipe fixture result_bytes=240 against the enabled minimum248. VM/test reproduction is intentionally unrun here.

Expected and actual behavior

Explicit storage should admit the original two complete plans and only then exercise intended pool exhaustion. Old capacities are smaller than those complete canonical inputs; stale non-pipe reply capacity also refuses fixture construction. With the new client80 layout the unchanged counts require client plans508 each/1016 total and binding plans1916 each/3832 total. The fix updates all original configs and independent literal oracles, preserves groups, native/client/fd/ring counts and finite timeouts, and keeps reply capacity248 explicit.

Environment and identity

  • Component repository/revision and Integration source graph: integration original source, Integration original graph.
  • Image profile, digest and build/runtime configuration: selected native realm witness sources; no image built or runtime digest collected for this finding.
  • Hardware or VM, architecture, firmware and toolchain versions: x86_64 source contracts; no guest/toolchain execution performed.
  • Input/session route and granted authority relevant to reproduction: original explicit configuration owner and retained realm fixtures; capacity metadata grants no authority.
  • Last known working revision, if known: not established.

Evidence and prior checks

Read-only arithmetic and original selected source expose these stale inputs. No executed VM/test result, new CI regression attribution or timeout observation is claimed. Existing failures remain retained; the new factory path and complete guest-build acceptance remain separate.

Tracking

Full native thread scope, phase completion, owning review. Signed source fix and exact immutable graph adoption will be recorded before closure.

Complete native factory delivery, ordinary creation and full EriX/toolchain guest acceptance remain open.

## Summary Realm witnesses retain undersized canonical plan and stale reply budgets. This prevents the original source witness from reaching its intended admission boundary. ## Reproduction Inspect runtime.realm-clients.vm.toml and runtime.realm-owner-loss.vm.toml (realm_plan_bytes=968), plus the bindings/FAT/exFAT configurations (3752), against their selected canonical header/client/group counts. Before this migration, header144/client72 already require two 492-byte client plans (984 total), and two 1900-byte binding plans (3800 total). Also inspect the selected Posixd non-pipe fixture result_bytes=240 against the enabled minimum248. VM/test reproduction is intentionally unrun here. ## Expected and actual behavior Explicit storage should admit the original two complete plans and only then exercise intended pool exhaustion. Old capacities are smaller than those complete canonical inputs; stale non-pipe reply capacity also refuses fixture construction. With the new client80 layout the unchanged counts require client plans508 each/1016 total and binding plans1916 each/3832 total. The fix updates all original configs and independent literal oracles, preserves groups, native/client/fd/ring counts and finite timeouts, and keeps reply capacity248 explicit. ## Environment and identity - Component repository/revision and Integration source graph: [integration original source](https://git.erikinkinen.fi/erix/integration/commit/ab8d58b51b8071179a374947c1d1b67a748aaa6e), [Integration original graph](https://git.erikinkinen.fi/erix/integration/commit/ab8d58b51b8071179a374947c1d1b67a748aaa6e). - Image profile, digest and build/runtime configuration: selected native realm witness sources; no image built or runtime digest collected for this finding. - Hardware or VM, architecture, firmware and toolchain versions: x86_64 source contracts; no guest/toolchain execution performed. - Input/session route and granted authority relevant to reproduction: original explicit configuration owner and retained realm fixtures; capacity metadata grants no authority. - Last known working revision, if known: not established. ## Evidence and prior checks Read-only arithmetic and original selected source expose these stale inputs. No executed VM/test result, new CI regression attribution or timeout observation is claimed. Existing failures remain retained; the new factory path and complete guest-build acceptance remain separate. ## Tracking [Full native thread scope](https://git.erikinkinen.fi/erix/kernel/issues/47), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65), [owning review](https://git.erikinkinen.fi/erix/integration/pulls/12). Signed source fix and exact immutable graph adoption will be recorded before closure. Complete native factory delivery, ordinary creation and full EriX/toolchain guest acceptance remain open.
erikinkinen 2026-10-12 11:03:35 +02:00
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:17 +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/integration#103
No description provided.