[BUG] Native byte-client scratch rejects complete filesystem requests #31

Closed
opened 2026-10-02 07:50:56 +02:00 by erikinkinen · 0 comments
Owner

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 in src/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 revision e4c1478f60. 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
Repository Links
posixd issue 31, temporary-output.md
## 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 in `src/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 revision e4c1478f605662c0f7792ba4eb08687c613b1b4b. 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](https://git.erikinkinen.fi/erix/posixd/issues/30) and [Posixd review](https://git.erikinkinen.fi/erix/posixd/pulls/5). Track overall acceptance in [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). ### 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. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | posixd | [issue 31](https://git.erikinkinen.fi/erix/posixd/issues/31), [temporary-output.md](https://git.erikinkinen.fi/erix/posixd/src/branch/feature/posix-compat/docs/temporary-output.md) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:07 +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/posixd#31
No description provided.