Bind exact entries through retained parents #31
No reviewers
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/ramfsd!31
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/retained-parent-entry-bindings"
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?
Select entries through actual retained RAM parents and apply effects through their original bindings. Preserve parent ceilings and cleanup custody without resolving the target again from a path.
Depends on #30 and the IPC #111 provider cohort. Part of Vfsd native ownership.
Cross-provider and release-image rollout remains tracked in the owning Vfsd issue.
WIP: Bind exact entries through retained parentsto Bind exact entries through retained parentsThe retained-parent component is ready for review. Parent freshness is checked against an actual permission change; bounded parent navigation does not permit symlink traversal or escape. Explicit touch intent, refusal nonmutation and original-key cleanup are preserved.