[BUG] Acquisition scope controls cross module privacy and miss navigation import #19
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/vfsd#19
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
Acquisition-scope controls compiled beneath the redirection fixture refer to
ScopeStart without importing it and read or mutate AcquisitionScope's private
root/current fields from a sibling module. These source references prevent the
authored control family from compiling at the affected revision.
Reproduction
Source-derived reproduction, not an executed compiler run: inspect the test
module tree in redirection_tests.rs, acquisition_scope/tests.rs and
acquisition_scope/component_tests.rs at the affected revision. ScopeStart is
not imported into that ancestry. AcquisitionScope declares root/current privately
in acquisition_scope.rs, while these controls are children of redirection_tests.
The existing node accessor supplies read-only observations. No test or build
command was run under the current execution waiver.
Expected and actual behavior
Expected: controls import the actual navigation enum, observe nodes through the
existing accessor and inject descriptive route faults without making original
custody fields public in production.
Actual, established from source: the enum reference lacks an import and direct
field accesses cross module privacy. No compiler diagnostics or runtime failure
is presented as executed evidence. Repair the imports and accessor usage, and
use a narrowly scoped test-only route fault injector for the negative control.
Environment and identity
e4af4b056b; Integration 00a17bcea0bb415d1b283c78998d9071a5334e02.Evidence and prior checks
Source module declarations, the private AcquisitionScope fields, and their
sibling test references establish the mismatch. The repair retains the
independent original-custody controls and the negative route-refusal scenario.
Test execution, builds and CI observation remain deferred; no pass is claimed.
Tracking
Related work: retained cwd migration,
Vfsd review, and the
phase completion tracker.
Source resolution
Fixed in signed and pushed Vfsd
b97a0ce9.The control module imports ScopeStart explicitly and reads root/current through
the existing node accessor. The negative route-refusal control uses a narrow
cfg(test)-only current-mount fault injector; production owner fields stay private.
Original provider custody is unchanged by fault injection. All affected controls
remain present and unrun as part of the 41-control fixture migration. Closed as
source-complete under the testing/CI waiver; no compiler execution, test pass or
runtime publication is claimed. The broader migration remains in
Vfsd#16.
erikinkinen referenced this issue2026-10-01 15:31:56 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 15:31:59 +02:00
erikinkinen referenced this issue2026-10-01 15:32:00 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 15:32:00 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 15:32:01 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-01 15:32:02 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-01 15:32:02 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-10-01 15:32:03 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-01 15:32:03 +02:00
erikinkinen referenced this issue from erix/fatd2026-10-01 15:32:03 +02:00