[BUG] Binding policy control retains obsolete RAM capacity and mount expectations #102

Closed
opened 2026-10-02 02:20:29 +02:00 by erikinkinen · 0 comments
Owner

Summary

The binding-scenario host control rejects the current deliberate nested RAM mount and its independently budgeted pins. Its expectation remained at 30 RAM handles after the actual policy moved to 41. This is a source-confirmed control regression; no execution result is claimed.

Reproduction

At Integration cd25722937d24e34e0ba9e7b5985374943fefcec, compare tests/realm_bindings_scenario_test.py with tests/runtime-configs/runtime.realm-bindings.vm.toml. The former asserts 30 handles and complete equality after normalizing only prior differences; the latter declares 41 and an additional read-only RAM mount. The relevant command, when testing resumes, is python3 -B -W error tests/realm_bindings_scenario_test.py.

Expected and actual behavior

The control should admit exactly the documented original-source capacities and nested mount while rejecting unrelated policy changes. Its literal equality currently contradicts the checked-in inputs. The correction accounts for three mount/root/parent pins and eight simultaneous client branch pins, asserts the complete additional mount policy, then compares the remaining configuration unchanged.

Environment and identity

  • Component repository/revision and Integration source graph: Integration revision above; this is a host fixture-policy control.
  • Image profile, digest and build/runtime configuration: tests/runtime-configs/runtime.realm-bindings.vm.toml; no image was built.
  • Hardware or VM, architecture, firmware and toolchain versions: not required for this direct source contradiction.
  • Input/session route and granted authority relevant to reproduction: explicit TOML policy; no native grant is changed by the correction.
  • Last known working revision, if known: not established.

Evidence and prior checks

Source inspection only. Testing, builds and CI observation remain deferred by user instruction. The 41-handle value comprises 30 existing handles, three namespace pins and eight client branch pins. No failed run, timeout or passing rerun is claimed.

Tracking

Related: #65 and #12; compatibility namespace completion. Acceptance is correction of the stale assertion while retaining exact policy comparison. Execution remains separately deferred.

Cross-provider filesystem lifetime — signed source acceptance, 2 October 2026

Two live binding scenarios cover RAM, ext and separately selected FAT32/exFAT: conditional replacement/unlink, retained aliases and original identities, moved/detached directories, name reuse, supported links and read-only, cross-filesystem and unsupported-link refusals. Final media observers require reclaimed allocations, consistent reverse indices and clear undo ownership.

Both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.

Phase progress: 19.12% weighted, 7.61% whole acceptance; 27/460 parents and 485/949 sub-items.

Related records and contracts
Repository Links
docs PR 4
integration issue 102, PR 12
posixd PR 5
vfsd issue 16, PR 3
## Summary The binding-scenario host control rejects the current deliberate nested RAM mount and its independently budgeted pins. Its expectation remained at 30 RAM handles after the actual policy moved to 41. This is a source-confirmed control regression; no execution result is claimed. ## Reproduction At Integration `cd25722937d24e34e0ba9e7b5985374943fefcec`, compare `tests/realm_bindings_scenario_test.py` with `tests/runtime-configs/runtime.realm-bindings.vm.toml`. The former asserts 30 handles and complete equality after normalizing only prior differences; the latter declares 41 and an additional read-only RAM mount. The relevant command, when testing resumes, is `python3 -B -W error tests/realm_bindings_scenario_test.py`. ## Expected and actual behavior The control should admit exactly the documented original-source capacities and nested mount while rejecting unrelated policy changes. Its literal equality currently contradicts the checked-in inputs. The correction accounts for three mount/root/parent pins and eight simultaneous client branch pins, asserts the complete additional mount policy, then compares the remaining configuration unchanged. ## Environment and identity - Component repository/revision and Integration source graph: Integration revision above; this is a host fixture-policy control. - Image profile, digest and build/runtime configuration: `tests/runtime-configs/runtime.realm-bindings.vm.toml`; no image was built. - Hardware or VM, architecture, firmware and toolchain versions: not required for this direct source contradiction. - Input/session route and granted authority relevant to reproduction: explicit TOML policy; no native grant is changed by the correction. - Last known working revision, if known: not established. ## Evidence and prior checks Source inspection only. Testing, builds and CI observation remain deferred by user instruction. The 41-handle value comprises 30 existing handles, three namespace pins and eight client branch pins. No failed run, timeout or passing rerun is claimed. ## Tracking Related: #65 and #12; [compatibility namespace completion](https://git.erikinkinen.fi/erix/posixd/issues/27). Acceptance is correction of the stale assertion while retaining exact policy comparison. Execution remains separately deferred. ### Cross-provider filesystem lifetime — signed source acceptance, 2 October 2026 Two live binding scenarios cover RAM, ext and separately selected FAT32/exFAT: conditional replacement/unlink, retained aliases and original identities, moved/detached directories, name reuse, supported links and read-only, cross-filesystem and unsupported-link refusals. Final media observers require reclaimed allocations, consistent reverse indices and clear undo ownership. Both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed. Phase progress: **19.12% weighted**, 7.61% whole acceptance; 27/460 parents and 485/949 sub-items. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | docs | [PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4) | | integration | [issue 102](https://git.erikinkinen.fi/erix/integration/issues/102), [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12) | | posixd | [PR 5](https://git.erikinkinen.fi/erix/posixd/pulls/5) | | vfsd | [issue 16](https://git.erikinkinen.fi/erix/vfsd/issues/16), [PR 3](https://git.erikinkinen.fi/erix/vfsd/pulls/3) | </details>
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#102
No description provided.