[BUG] Native byte-client scratch rejects complete filesystem requests #31
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/posixd#31
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
The native byte-client call helper reserves only 72 request bytes even though existing creation, permission and namespace workloads submit longer complete frames. ByteCall correctly refuses inadequate storage before submission, so those workloads cannot reach their intended native effects.
Reproduction
Inspect
src/byte_client/native.rs(call) and the generation-qualified path construction insrc/byte_client/witness/open/creation.rs. Combine the complete path bytes with the compatibility Open header and request prefix. The required frame exceeds the helper's fixed scratch array. Two-path namespace frames require still more storage.Expected and actual behavior
The helper should use explicit producer-admitted workspace capacity for the complete request. Currently its historical 32-byte payload assumption imposes an unrelated 72-byte limit before submission. Keep transport preflight and original caller cleanup; do not expand capabilities or fabricate a successful result.
Environment and identity
Source observation on
feature/posix-compat, Posixd revisione4c1478f60. This is a source-proven capacity mismatch; no runtime failure, test result or CI result is claimed.Evidence and prior checks
The constant request scratch and full path/frame lengths are directly inspectable. Tests, builds, lint, generated documentation, VM/profiler execution and CI observation remain deferred under the execution waiver. Add an authored control for complete long frames and preserve unchanged packet result bytes through retirement.
Tracking
Repair alongside temporary objects and atomic outputs and Posixd review. Track overall acceptance in phase completion.
Temporary objects and atomic output completion — 2 October 2026
Full libc integration, both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Related records and contracts
erikinkinen referenced this issue from erix/docs2026-10-02 08:05:41 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 08:05:42 +02:00
erikinkinen referenced this issue2026-10-02 08:05:43 +02:00
erikinkinen referenced this issue from erix/rootd2026-10-02 08:05:44 +02:00