[BUG] Detached directory reports depend on unrelated mounted roots #37
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#37
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
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/bindirectory on the same provider as/work. Configure a mounted/work/bootsibling whose root acquisition refuses withINTERNAL. Removebinfrom 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.
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.