[BUG] Native FAT parent observations retain the old parent after directory moves #11

Closed
opened 2026-10-01 09:29:21 +02:00 by erikinkinen · 0 comments
Owner

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

  • Component: Fatd 8bb010ea.
  • Integration: 5db754c7.
  • Selected original FAT/exFAT catalog and undo, native component and conditional namespace families.
  • Explicit original provider storage route and retained root/child handles; no image or VM run in this pass.
  • Last known working revision: unknown; no executed regression bisect.

Evidence and prior checks

Source inspection of store/native.rs and store/native/directory.rs shows parent selection through navigation_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
Repository Links
docs PR 4
fatd issue 11, detached-objects.md#current-parent-observations
integration PR 12
## 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 - Component: [Fatd 8bb010ea](https://git.erikinkinen.fi/erix/fatd/commit/8bb010ea0b312959848c92c57cbf8cfb3d060db4). - Integration: [5db754c7](https://git.erikinkinen.fi/erix/integration/commit/5db754c7fd5ed58e7423e52e4b3ab87a65e1c2b3). - Selected original FAT/exFAT catalog and undo, native component and conditional namespace families. - Explicit original provider storage route and retained root/child handles; no image or VM run in this pass. - Last known working revision: unknown; no executed regression bisect. ## Evidence and prior checks Source inspection of `store/native.rs` and `store/native/directory.rs` shows parent selection through `navigation_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](https://git.erikinkinen.fi/erix/posixd/issues/27), [provider review](https://git.erikinkinen.fi/erix/fatd/pulls/3), [phase requirements](https://git.erikinkinen.fi/erix/integration/issues/65). 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. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | docs | [PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4) | | fatd | [issue 11](https://git.erikinkinen.fi/erix/fatd/issues/11), [detached-objects.md#current-parent-observations](https://git.erikinkinen.fi/erix/fatd/src/branch/feature/posix-compat/docs/detached-objects.md#current-parent-observations) | | integration | [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:00 +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/fatd#11
No description provided.