[BUG] Native Result import shadows the provider test result type #15

Closed
opened 2026-09-30 16:55:03 +02:00 by erikinkinen · 0 comments
Owner

Summary

Vfsd's native provider test adapter imports lib_ipc::*, bringing the one-parameter native Result<T> alias into scope. Its file_call method declares Result<usize, u32>. This source type-arity mismatch prevents the existing scoped file controls from compiling as written. Explicit imports preserve the intended standard result type and provider error domain.

Reproduction

At Vfsd 61c54520b2eee6c852c5c224dbe59e2673f15720, inspect src/acquisition_scope/file_transport.rs: its wildcard import and two-parameter result signature conflict with the alias in LibIPC src/error.rs, publicly exported by src/lib.rs. The parent test adapter imports no explicit standard Result alias. Compile the supported Vfsd unit-test target when testing is re-enabled; no compiler command or reproduction was executed for this report.

Expected and actual behavior

Expected: the adapter returns the standard two-parameter result and explicitly imports the native framing it uses. Actual source: the native one-parameter alias shadows the prelude type. This is a source observation; no compiler diagnostic, exit status or runtime result is claimed.

Environment and identity

  • Vfsd: 61c54520b2eee6c852c5c224dbe59e2673f15720; LibIPC: bebb7a740d1eb665e7325e5c6f3a7a0ec501032d.
  • Integration graph: be7e5cbb5f1041fafa44a70df6da38e02db2ad88.
  • Image, VM and toolchain: no execution for this audit.
  • Authority: import repair adds no capability, route or ownership.
  • Last known working revision: not established.

Evidence and prior checks

The alias, import and signature are direct source evidence. The earlier Posixd import repair covered different files; the broader source scan now includes numeric error types. Testing, builds, lint checks and CI observation remain deferred by user instruction.

The expanded source inventory also confirms the same module-level collision in src/acquisition_scope/creation_transport.rs, src/acquisition_scope/directory_transport.rs, src/acquisition_scope/mount_installation_tests.rs, src/acquisition_scope/namespace_parent_tests.rs, src/backend_link.rs, src/backend_mount.rs, src/handles/namespace.rs, src/mount_test_transport.rs, src/mounts/native/walk.rs, src/scope_candidate_io.rs, src/scope_directory_io.rs, src/scope_link.rs. These modules now explicitly select core::result::Result, while the originally reported file adapter uses explicit native imports. Existing Loaderd standard imports and function-local native globs whose enclosing signatures are outside that scope are non-defects and remain unchanged. This repair does not execute compiler or runtime validation.

Tracking

Related work: original status and directories, Vfsd review, and phase completion. Close after the import repair and coherent signed publication; test execution is waived.

Original special-inode metadata — 30 September 2026

No device, socket, pipe, clock or new provider endpoint is granted.

The full status/directory item remains open for complete FAT metadata, pipe/stream status, the compatibility special-device-number field and remaining full-item integration. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Related records and contracts
Repository Links
docs PR 4
e2fsd issue 15, PR 3
fatd issue 6, PR 3
integration PR 12
lib-ipc PR 2
lib-posixabi PR 3
posixd PR 5
ramfsd issue 6, PR 2
rootd PR 2
vfsd issue 15
## Summary Vfsd's native provider test adapter imports `lib_ipc::*`, bringing the one-parameter native `Result<T>` alias into scope. Its `file_call` method declares `Result<usize, u32>`. This source type-arity mismatch prevents the existing scoped file controls from compiling as written. Explicit imports preserve the intended standard result type and provider error domain. ## Reproduction At Vfsd `61c54520b2eee6c852c5c224dbe59e2673f15720`, inspect `src/acquisition_scope/file_transport.rs`: its wildcard import and two-parameter result signature conflict with the alias in LibIPC `src/error.rs`, publicly exported by `src/lib.rs`. The parent test adapter imports no explicit standard Result alias. Compile the supported Vfsd unit-test target when testing is re-enabled; no compiler command or reproduction was executed for this report. ## Expected and actual behavior Expected: the adapter returns the standard two-parameter result and explicitly imports the native framing it uses. Actual source: the native one-parameter alias shadows the prelude type. This is a source observation; no compiler diagnostic, exit status or runtime result is claimed. ## Environment and identity - Vfsd: `61c54520b2eee6c852c5c224dbe59e2673f15720`; LibIPC: `bebb7a740d1eb665e7325e5c6f3a7a0ec501032d`. - Integration graph: `be7e5cbb5f1041fafa44a70df6da38e02db2ad88`. - Image, VM and toolchain: no execution for this audit. - Authority: import repair adds no capability, route or ownership. - Last known working revision: not established. ## Evidence and prior checks The alias, import and signature are direct source evidence. The earlier [Posixd import repair](https://git.erikinkinen.fi/erix/posixd/issues/26) covered different files; the broader source scan now includes numeric error types. Testing, builds, lint checks and CI observation remain deferred by user instruction. The expanded source inventory also confirms the same module-level collision in `src/acquisition_scope/creation_transport.rs`, `src/acquisition_scope/directory_transport.rs`, `src/acquisition_scope/mount_installation_tests.rs`, `src/acquisition_scope/namespace_parent_tests.rs`, `src/backend_link.rs`, `src/backend_mount.rs`, `src/handles/namespace.rs`, `src/mount_test_transport.rs`, `src/mounts/native/walk.rs`, `src/scope_candidate_io.rs`, `src/scope_directory_io.rs`, `src/scope_link.rs`. These modules now explicitly select `core::result::Result`, while the originally reported file adapter uses explicit native imports. Existing Loaderd standard imports and function-local native globs whose enclosing signatures are outside that scope are non-defects and remain unchanged. This repair does not execute compiler or runtime validation. ## Tracking Related work: [original status and directories](https://git.erikinkinen.fi/erix/posixd/issues/25), [Vfsd review](https://git.erikinkinen.fi/erix/vfsd/pulls/3), and [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). Close after the import repair and coherent signed publication; test execution is waived. ### Original special-inode metadata — 30 September 2026 No device, socket, pipe, clock or new provider endpoint is granted. The [full status/directory item](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open for complete FAT metadata, pipe/stream status, the compatibility special-device-number field and remaining full-item integration. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | docs | [PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4) | | e2fsd | [issue 15](https://git.erikinkinen.fi/erix/e2fsd/issues/15), [PR 3](https://git.erikinkinen.fi/erix/e2fsd/pulls/3) | | fatd | [issue 6](https://git.erikinkinen.fi/erix/fatd/issues/6), [PR 3](https://git.erikinkinen.fi/erix/fatd/pulls/3) | | integration | [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12) | | lib-ipc | [PR 2](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2) | | lib-posixabi | [PR 3](https://git.erikinkinen.fi/erix/lib-posixabi/pulls/3) | | posixd | [PR 5](https://git.erikinkinen.fi/erix/posixd/pulls/5) | | ramfsd | [issue 6](https://git.erikinkinen.fi/erix/ramfsd/issues/6), [PR 2](https://git.erikinkinen.fi/erix/ramfsd/pulls/2) | | rootd | [PR 2](https://git.erikinkinen.fi/erix/rootd/pulls/2) | | vfsd | [issue 15](https://git.erikinkinen.fi/erix/vfsd/issues/15) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35: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/vfsd#15
No description provided.