bug: Replace removed creation access field in Open response handling #35

Closed
opened 2026-10-02 21:41:12 +02:00 by erikinkinen · 0 comments
Owner

Summary

The creation-intent migration changed VfsCreateCandidateRequestV1 from an access field to FsCreationIntentV1, but Posixd's successful Open creation-response handler still reads request.access. The selected source graph therefore contains a Rust member access to a field that no longer exists. This prevents compilation of that handler; no compiler run has been performed under the current execution waiver.

Reproduction

Inspect Posixd revision 06caf3e57c, src/realm_io/external/path_call/response.rs, in the Request::Create success branch. It assigns incoming.access = Some(request.access). The request comes from wire::create and is a VfsCreateCandidateRequestV1. Inspect the selected LibIPC revision 168a3d85569eabed2bfb097a109c4b98b8ae37c1, src/body/vfs_candidate_creation.rs: the corresponding field is now intent: FsCreationIntentV1, with no access field. This mismatch is present in committed source and needs no runtime input to expose by inspection. Build reproduction is deferred.

Expected and actual behavior

Expected: successful regular-file creation retains exactly the File(access) intent that the original conditional request sent and its correlated result accepted. Socket intent must not acquire regular-file access by numeric conversion or defaulting.

Actual: response handling refers to the removed field. There is no executed diagnostic, exit status, VM result or CI observation to report. The observed source mismatch is definite; downstream build impact has not been executed.

Environment and identity

  • Component repository/revision and Integration source graph: Posixd 06caf3e57c, selected by Integration b0fd5eb12a39c57a7f7104bdd3a6bb72611f692b; LibIPC 168a3d85569eabed2bfb097a109c4b98b8ae37c1.
  • Image profile, digest and build/runtime configuration: no image built or run for this finding; source-level conditional Open creation handler.
  • Hardware or VM, architecture, firmware and toolchain versions: not exercised; no toolchain execution used as evidence.
  • Input/session route and granted authority relevant to reproduction: existing original acquisition scope and conditional creation; no new grant needed.
  • Last known working revision, if known: not established by execution. The source mismatch entered when Posixd ad8bbaf3b0 adopted the creation-intent codec while this response handler remained unchanged.

Evidence and prior checks

Committed response handler and selected request declaration establish the mismatch. Source inspection distinguishes the valid request.access use in the separate VfsAdmitCandidateRequestV1 branch from this stale creation field. Tests, builds, lint and CI observation remain deferred.

Tracking

Related: local stream sockets, Posixd review, Phase 6 completion. Repair the producer/consumer source mismatch, preserve all three file access modes and retained native cleanup, and add an authored behavioral regression without claiming an executed pass.

Creation-response regression repair — 2 October 2026

Socket intent cannot become regular-file access.

Component status documents record
the repair; unchanged runtime/API behavior requires no new manual contract.

Whole socket completion remains open: scoped named
connections, original admission, counted backlog and concurrent calls still need
implementation. Full EriX and external Rust/LLVM guest rebuilding remain required
and unperformed. No checklist acceptance credit is added for this repair.

Related records and contracts
Repository Links
posixd issue 35
## Summary The creation-intent migration changed VfsCreateCandidateRequestV1 from an access field to FsCreationIntentV1, but Posixd's successful Open creation-response handler still reads request.access. The selected source graph therefore contains a Rust member access to a field that no longer exists. This prevents compilation of that handler; no compiler run has been performed under the current execution waiver. ## Reproduction Inspect Posixd revision 06caf3e57cd57f277a094992a5b674a4bc1251fd, src/realm_io/external/path_call/response.rs, in the Request::Create success branch. It assigns incoming.access = Some(request.access). The request comes from wire::create and is a VfsCreateCandidateRequestV1. Inspect the selected LibIPC revision 168a3d85569eabed2bfb097a109c4b98b8ae37c1, src/body/vfs_candidate_creation.rs: the corresponding field is now intent: FsCreationIntentV1, with no access field. This mismatch is present in committed source and needs no runtime input to expose by inspection. Build reproduction is deferred. ## Expected and actual behavior Expected: successful regular-file creation retains exactly the File(access) intent that the original conditional request sent and its correlated result accepted. Socket intent must not acquire regular-file access by numeric conversion or defaulting. Actual: response handling refers to the removed field. There is no executed diagnostic, exit status, VM result or CI observation to report. The observed source mismatch is definite; downstream build impact has not been executed. ## Environment and identity - Component repository/revision and Integration source graph: Posixd 06caf3e57cd57f277a094992a5b674a4bc1251fd, selected by Integration b0fd5eb12a39c57a7f7104bdd3a6bb72611f692b; LibIPC 168a3d85569eabed2bfb097a109c4b98b8ae37c1. - Image profile, digest and build/runtime configuration: no image built or run for this finding; source-level conditional Open creation handler. - Hardware or VM, architecture, firmware and toolchain versions: not exercised; no toolchain execution used as evidence. - Input/session route and granted authority relevant to reproduction: existing original acquisition scope and conditional creation; no new grant needed. - Last known working revision, if known: not established by execution. The source mismatch entered when Posixd ad8bbaf3b0157da72a0d4e7373cea34171da918d adopted the creation-intent codec while this response handler remained unchanged. ## Evidence and prior checks [Committed response handler](https://git.erikinkinen.fi/erix/posixd/src/commit/06caf3e57cd57f277a094992a5b674a4bc1251fd/src/realm_io/external/path_call/response.rs) and [selected request declaration](https://git.erikinkinen.fi/erix/lib-ipc/src/commit/168a3d85569eabed2bfb097a109c4b98b8ae37c1/src/body/vfs_candidate_creation.rs) establish the mismatch. Source inspection distinguishes the valid request.access use in the separate VfsAdmitCandidateRequestV1 branch from this stale creation field. Tests, builds, lint and CI observation remain deferred. ## Tracking Related: [local stream sockets](https://git.erikinkinen.fi/erix/posixd/issues/34), [Posixd review](https://git.erikinkinen.fi/erix/posixd/pulls/5), [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Repair the producer/consumer source mismatch, preserve all three file access modes and retained native cleanup, and add an authored behavioral regression without claiming an executed pass. ### Creation-response regression repair — 2 October 2026 Socket intent cannot become regular-file access. Component status documents record the repair; unchanged runtime/API behavior requires no new manual contract. Whole socket completion remains open: scoped named connections, original admission, counted backlog and concurrent calls still need implementation. Full EriX and external Rust/LLVM guest rebuilding remain required and unperformed. No checklist acceptance credit is added for this repair. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | posixd | [issue 35](https://git.erikinkinen.fi/erix/posixd/issues/35) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:08 +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#35
No description provided.