[BUG] Counted native name storage rejects valid non-UTF-8 basenames #11
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/ramfsd#11
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
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
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.
erikinkinen referenced this issue2026-10-30 18:06:28 +01:00
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.