bug: Replace removed creation access field in Open response handling #35
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#35
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 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
06caf3e57c, selected by Integration b0fd5eb12a39c57a7f7104bdd3a6bb72611f692b; LibIPC 168a3d85569eabed2bfb097a109c4b98b8ae37c1.ad8bbaf3b0adopted 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
erikinkinen referenced this issue2026-10-02 21:46:05 +02:00
erikinkinen referenced this issue from erix/rootd2026-10-02 21:46:06 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 21:46:06 +02:00