[BUG] Native FAT parent observations retain the old parent after directory moves #11
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/fatd#11
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
After moving a selected-catalog FAT/exFAT directory to a different parent, native
..acquisition and directory parent observations still select the handle's original entering parent. The rename updates the original catalog parent identity, but those readers do not consume it. This is a source-confirmed semantic defect; no runtime reproduction has been executed.Reproduction
Retain a native acquisition for a child under one directory, move that child beneath another directory using the conditional rename family, and request
..or the parent directory observation through the original child handle. Cover both selected FAT and exFAT media. Provider regression controls will be authored over the existing independent fixtures; test execution remains deferred.Expected and actual behavior
Expected: both observations identify the actual new parent while respecting the original retained root ceiling. Original object aliases and cleanup must remain valid through the move. Source-observed behavior: both readers follow the pre-rename entering-parent handle, despite the catalog recording the destination parent. Mounted roots must still clamp parent traversal, and detached directories must keep their admitted original parent.
Environment and identity
Evidence and prior checks
Source inspection of
store/native.rsandstore/native/directory.rsshows parent selection throughnavigation_parent; rename/catalog completion updates the original parent serial separately. Repair should share one admitted original catalog ancestry reader for lookup and parent observations. Tests, builds, lint checks, VM/profiler execution and CI observation remain deferred; no pass is claimed.Tracking
Conditional namespace and lifetime feature, provider review, phase requirements. This prerequisite repair does not itself complete the legacy cwd migration.
Current FAT parent observations after moves — 1 October 2026
Ordinary selected acquisitions no longer keep obsolete entering handles; pending entry roles and imported media preserve their required custody.
Four additional provider controls cover both FAT and exFAT: moved directories and old-parent reclamation, aliases/repeated moves, detached parents after entering handles retire, root clamping and cyclic ancestry refusal.
Vfsd cwd/launch/exact/redirection consumers still reconstruct path spellings; their migration must precede removal of spelling pins. Complete cross-provider lifetime controls also remain open. Checklist acceptance is unchanged: 18.82% weighted, 6.81% whole-item; 25/460 parents and 473/943 sub-items across 165 decomposed parents.
Both full EriX guest build generations and external Rust/LLVM rebuilding remain required and unperformed.
Related records and contracts
erikinkinen referenced this issue2026-10-01 09:37:39 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 09:37:39 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 09:37:39 +02:00