[BUG] Acquisition metadata fixtures confuse retained sources and object aliases #20
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#20
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
Native acquisition metadata controls choose the first provider component instead
of the requested file, and a root/cwd control assigns distinct inode observations
to two references to the same actual object. Real source custody makes these
assumptions invalid, so these controls cannot establish the stated routing and
identity properties.
Reproduction
Source-derived reproduction, not an executed test: inspect
acquisition_scope/metadata_tests.rs and cwd/native/fixture.rs at Vfsd
62f347280e. The shared bootstrap keeps an originalwork-directory candidate. The file fixture then acquires another candidate, while
metadata controls choose components.iter().next() instead of that file's identity.
The file scope has equal root and cwd objects; writing separate observations under
their identical handle key overwrites the first observation.
Expected and actual behavior
Expected: independently scripted provider objects supply metadata for the actual
selected file, root and cwd. Aliases of one object agree; distinct root/cwd controls
acquire genuinely distinct directories.
Actual, established from source: map order can select the source directory, and
the root/cwd control expects conflicting serials from one map key. No compiler,
test failure, exit status or runtime reproduction is claimed. Repair the controls
using literal provider identities and real contextual cwd derivation; retain
independent cleanup and add alias-lifetime coverage.
Environment and identity
62f347280e; Integration 00a17bcea0bb415d1b283c78998d9071a5334e02.Evidence and prior checks
The actual fixture bootstrap, file-scope producer and map-key assignments establish
the mismatch. Testing, builds and CI observation remain deferred. Source repair
and additional authored controls do not establish an execution pass.
Tracking
Related: retained cwd migration,
Vfsd review, and the
phase completion tracker.
Source-complete repair is signed and pushed in
Vfsd 812a205c,
with the updated contract in
Docs 20649047.
Metadata now follows independently scripted object identity. Distinct root/cwd
observations use actual cwd derivation, and a new control preserves one inode
observation through source and sibling retirement. Original file effects are
selected explicitly, and scope teardown observes the actual receiver. The six
metadata controls, among 36 updated acquisition-family controls, remain authored
and unrun. Closed as source-complete under the testing/CI waiver; no execution
pass is claimed.
erikinkinen referenced this issue2026-10-01 15:55:41 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 15:55:44 +02:00
erikinkinen referenced this issue2026-10-01 15:55:44 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 15:55:45 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 15:55:46 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-01 15:55:47 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-01 15:55:47 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-10-01 15:55:47 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-01 15:55:48 +02:00
erikinkinen referenced this issue from erix/fatd2026-10-01 15:55:48 +02:00