[BUG] Accept live handle records in retained permission and resize helpers #3
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#3
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
The retained permission and truncation helpers accept
HandleMetadata, the construction-only descriptor used when inserting a handle. Their callers pass theHandleRecordreturned bylookup_handle. These are distinct Rust value types, so the helper signatures do not match the actual retained-state path.Reproduction
Inspect
lookup_handleinsrc/instances.rs,describe_permissionsinsrc/instances/permissions.rsandtruncate_retained_nodeinsrc/instances/truncate.rs. Compare their declared argument/return types with calls frompermission_snapshot,truncate_if_permissionandtruncate_handle.Expected and actual behavior
Expected: helpers consume the already-resolved live handle record in the same exclusive state turn, preserving its mount/node identity without a second lookup or a conversion back to insertion metadata.
Actual in source: both helpers name construction metadata as their argument. Change those arguments/imports to the live
HandleRecord; keep all permission-revision, node-kind, bounds, timestamp and native caller obligations unchanged.Environment and identity
feature/posix-compat; signed starting revision0a82212d6f6f8c962f11673cbfb6bbdafba16cac.Evidence and prior checks
Conditional provider acquisition checkpoint: lib-ipc
bb5df3d2, lib-posixabicdc6eb9e, ramfsdba8ea6da, docsd470ea50, integrationb9acf76b, rootd27835abd.Compatibility 1.5 now describes Open/openat with raw borrowed pathname bytes and checked independent base, access, lookup, shared-status, inheritance and creation-mode domains. Private provider acquisition/retirement framing retains an original root and acquisition identity before submission. Ramfsd compares actual parent permission evidence and pins no-follow files, directories or symlinks in one exclusive turn. Cleanup does not require the original handle reply; retirement fences delayed replay without tombstone storage. Intermediate directory closure preserves independent children, and the original root cannot close while its pins remain.
Eighteen new controls are authored and unrun: five compatibility codecs, five private-provider codecs and eight actual Ramfsd state/dispatch cases. Ramfsd's live-handle helper types and stale compatibility-minor fixture expectations are corrected from source observations. No compiler or test failure is claimed. Component contracts and maintained manual/API-reference source are updated, and Rustfmt was applied.
Full native open/openat remains open: native source preparation, VFS candidate ownership, other providers, Posixd serving, creation/append effects and native workloads are unfinished. No acquisition acceptance credit is added. Weighted completion remains 16.91%, with 21/460 parents and 441/902 sub-items complete. Both EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.
Existing permission and conditional-resize controls exercise these paths, and are retained. Fix the source types alongside provider ownership work; do not replace actual retained identity with fabricated metadata. Tests and CI observation remain deferred by user instruction.
Tracking
Owning review: #2. Related native acquisition: erix/posixd#17. Phase tracking: erix/integration#65.
Ordinary V2 response correlation no longer admits retired effect operations.
They retain
root/parent/key fields, full-width handles and timestamps, optional trusted time,
explicit selected fields, invalid destination refusal and untouched short outputs. New literal stat controls cover framing, canaries and retired-family refusal. Retired numeric replies cannot satisfy ordinary V2 or native effect correlation. Vfsd's last old exported-name references become literal timestamp-adapter refusals
for all thirteen retired operations.
The existing superseded-bridge/provider-spelling-pin acceptance criterion in
the native ownership feature
is source-complete. Required imported FAT/exFAT binding and geometry guards remain. The remaining cwd/contextual-serving and complete lifecycle/control/graph criteria
need a current-source acceptance audit and any missing implementation, followed by
coherent runtime adoption. No synthetic weighted sub-item or full lifetime acceptance is added. Recomputed
phase progress remains 18.95% weighted and 6.81% whole acceptance: 25/460 parents
and 480/949 sub-items. Full EriX guest generations and external Rust/LLVM rebuilding
inside EriX remain required and unperformed.
Related records and contracts
erikinkinen referenced this issue from erix/docs2026-09-29 19:19:08 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 19:19:18 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-29 19:19:27 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-29 19:19:28 +02:00
erikinkinen referenced this issue2026-09-29 19:19:38 +02:00
erikinkinen referenced this issue2026-10-02 00:56:41 +02:00
erikinkinen referenced this issue from erix/docs2026-10-02 00:56:41 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-02 00:56:42 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-02 00:56:42 +02:00
erikinkinen referenced this issue from erix/vfsd2026-10-02 00:56:43 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-02 00:56:43 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 00:56:46 +02:00
erikinkinen referenced this issue from erix/fatd2026-10-02 01:34:40 +02:00
erikinkinen referenced this issue from erix/docs2026-10-02 01:34:42 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-02 01:34:44 +02:00
erikinkinen referenced this issue from erix/vfsd2026-10-02 01:34:44 +02:00
erikinkinen referenced this issue from erix/vfsd2026-10-02 01:34:45 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-02 01:34:46 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 01:34:50 +02:00