[BUG] Counted native name storage rejects valid non-UTF-8 basenames #11

Closed
opened 2026-10-12 13:52:19 +02:00 by erikinkinen · 1 comment
Owner

Summary

Counted native name storage rejects valid non-UTF-8 basenames. Maintained validation cannot reach its intended successful boundary.

Reproduction

Run the maintained retained-name and compaction provider control with the original 902-byte pool and a 601-byte basename containing only 0xff bytes. Use the explicitly granted original namespace operation. The original failing source and current repairs are distinct; failures and true exit statuses are retained.

Expected and actual behavior

Native basenames that fit the counted storage and contain no NUL, slash or dot component must retain their exact raw bytes. Names::reserve returns INVALID_ARGUMENT solely because the administrative validate_name API requires UTF-8. The native wire accepts raw component bytes, and the name fits the explicit pool.

Environment and identity

  • Component repository/revision and Integration source graph: original ramfsd source, original Integration graph.
  • Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report.
  • Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred.
  • Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced.
  • Last known working revision, if known: not established.

Evidence and prior checks

Use the shared native creation-component validator without UTF-8 conversion. Preserve complete byte budgets, shape refusals, compaction and original owner custody. All 185 provider units and strict host/freestanding checks pass. Signed fix: 15e2a11f.

Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.

Tracking

Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.

## Summary Counted native name storage rejects valid non-UTF-8 basenames. Maintained validation cannot reach its intended successful boundary. ## Reproduction Run the maintained retained-name and compaction provider control with the original 902-byte pool and a 601-byte basename containing only 0xff bytes. Use the explicitly granted original namespace operation. The original failing source and current repairs are distinct; failures and true exit statuses are retained. ## Expected and actual behavior Native basenames that fit the counted storage and contain no NUL, slash or dot component must retain their exact raw bytes. Names::reserve returns INVALID_ARGUMENT solely because the administrative validate_name API requires UTF-8. The native wire accepts raw component bytes, and the name fits the explicit pool. ## Environment and identity - Component repository/revision and Integration source graph: [original ramfsd source](https://git.erikinkinen.fi/erix/ramfsd/commit/6c408e89a49bdc5b41eb95d2753635901d2a0563), [original Integration graph](https://git.erikinkinen.fi/erix/integration/commit/a615de2f69c25d4575d0c349757a0017082f988b). - Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report. - Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred. - Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced. - Last known working revision, if known: not established. ## Evidence and prior checks Use the shared native creation-component validator without UTF-8 conversion. Preserve complete byte budgets, shape refusals, compaction and original owner custody. All 185 provider units and strict host/freestanding checks pass. Signed fix: [15e2a11f](https://git.erikinkinen.fi/erix/ramfsd/commit/15e2a11f390c7982bfa93f03967d8d91764edb4c). Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired. ## Tracking [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:11 +01:00
Author
Owner

The raw-name repair is ready for review in #32. Both counted reservation and retained rename now use the native component validator. The maintained 601-byte non-UTF-8, exact-pool capacity, alias and compaction controls pass without changing their byte budgets or namespace authority.

The raw-name repair is ready for review in #32. Both counted reservation and retained rename now use the native component validator. The maintained 601-byte non-UTF-8, exact-pool capacity, alias and compaction controls pass without changing their byte budgets or namespace authority.
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/ramfsd#11
No description provided.