[BUG] Detached directory reports depend on unrelated mounted roots #37

Open
opened 2026-10-18 13:18:33 +02:00 by erikinkinen · 1 comment
Owner

Summary

A detached ordinary directory's physical report still searches mounted overlays after its own provider reaches the end of the parent directory. An unrelated mount refusal can replace a legitimate unavailable-path result.

Reproduction

Hold an ordinary /work/bin directory on the same provider as /work. Configure a mounted /work/boot sibling whose root acquisition refuses with INTERNAL. Remove bin from the parent listing, then request its physical path through the held directory.

Expected and actual behavior

The path should be unavailable while the original directory remains usable. A mounted root on another retained route cannot match this child. The existing search nevertheless reaches the overlay and propagates its refusal. Fresh name/child identity checks and errors from the actual provider must remain intact.

Environment and identity

Affected source: Vfsd 066362ac. The focused protocol fixture uses independently supplied directory entries and provider refusals. No guest reproduction or last working revision is established.

Evidence and prior checks

Code inspection identifies the remaining overlay path. The hosted protocol fixture supplies a failing FAT sibling and directly covers this regression; its three follow-up controls are authored but have not compiled or run. The guest directory-script extension exercises detached physical reporting and retained dot/parent traversal with normal providers. It does not inject the unrelated provider refusal. CI390 passed before these controls existed.

Tracking

Related: held mounted-root reporting, implementation PR. This does not identify the producer of the separate FAT realm wire error.

  • Exclude overlays only when retained child and parent routes prove they cannot match.
  • Prove detached absence, raw rename/identity reuse, provider refusal, unchanged directory enumeration and cleanup.
  • Exercise detached physical reporting and retained dot/parent traversal in the maintained guest directory script with the updated source graph.
## Summary A detached ordinary directory's physical report still searches mounted overlays after its own provider reaches the end of the parent directory. An unrelated mount refusal can replace a legitimate unavailable-path result. ## Reproduction Hold an ordinary `/work/bin` directory on the same provider as `/work`. Configure a mounted `/work/boot` sibling whose root acquisition refuses with `INTERNAL`. Remove `bin` from the parent listing, then request its physical path through the held directory. ## Expected and actual behavior The path should be unavailable while the original directory remains usable. A mounted root on another retained route cannot match this child. The existing search nevertheless reaches the overlay and propagates its refusal. Fresh name/child identity checks and errors from the actual provider must remain intact. ## Environment and identity Affected source: [Vfsd 066362ac](https://git.erikinkinen.fi/erix/vfsd/commit/066362ac3339432414379b0fc7a1b662d661a035). The focused protocol fixture uses independently supplied directory entries and provider refusals. No guest reproduction or last working revision is established. ## Evidence and prior checks Code inspection identifies the remaining overlay path. The hosted protocol fixture supplies a failing FAT sibling and directly covers this regression; its three follow-up controls are authored but have not compiled or run. The guest directory-script extension exercises detached physical reporting and retained dot/parent traversal with normal providers. It does not inject the unrelated provider refusal. [CI390](https://git.erikinkinen.fi/erix/vfsd/actions/runs/390) passed before these controls existed. ## Tracking Related: [held mounted-root reporting](https://git.erikinkinen.fi/erix/vfsd/issues/36), [implementation PR](https://git.erikinkinen.fi/erix/vfsd/pulls/3). This does not identify the producer of the separate FAT realm wire error. - [x] Exclude overlays only when retained child and parent routes prove they cannot match. - [x] Prove detached absence, raw rename/identity reuse, provider refusal, unchanged directory enumeration and cleanup. - [ ] Exercise detached physical reporting and retained dot/parent traversal in the maintained guest directory script with the updated source graph.
Author
Owner

Implemented in 7f15b7f3. The hosted controls cover the failing FAT sibling, detached absence, raw rename/identity reuse, actual provider refusal and unchanged directory enumeration. Both local feature configurations pass all 549 tests; CI392 also passes. The guest lifecycle check still awaits the updated Integration graph and does not inject a provider refusal.

Implemented in [7f15b7f3](https://git.erikinkinen.fi/erix/vfsd/commit/7f15b7f3a39fcdad20052819c23a197a28d2c09b). The hosted controls cover the failing FAT sibling, detached absence, raw rename/identity reuse, actual provider refusal and unchanged directory enumeration. Both local feature configurations pass all 549 tests; [CI392](https://git.erikinkinen.fi/erix/vfsd/actions/runs/392) also passes. The guest lifecycle check still awaits the updated Integration graph and does not inject a provider refusal.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:20 +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/vfsd#37
No description provided.