[BUG] External operation cancellation rejects acknowledged route invalidation #13
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/posixd#13
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
Posixd's external-operation cleanup rejects an acknowledged native Draining(NOT_FOUND) transition as fatal. Route invalidation can legitimately produce that transition, so cancellation can stop with original custody retained instead of completing retirement. This is a source-confirmed reliability defect; no authority escape is claimed.
Reproduction
Arrange an external operation with an outstanding original outbound delivery. Invalidate the original native route before cancellation cleanup. Have RELEASE acknowledge Draining(NOT_FOUND), then inspect the same draining history and retire it. An analogous inbound RELINQUISH transition also reaches the overly narrow external-operation probe. These are deterministic host-fixture inputs to be authored with the correction; no runtime reproduction has been executed under the user's testing waiver.
Expected and actual behavior
Expected: recognize the acknowledged invalidation, retain both original owners while cleanup drains, accept canonical absence only after acknowledgement, and perform no repeated provider operation or client completion. Unknown failures and unacknowledged absence must retain quarantine.
Actual source behavior: external Caller::release accepts only Draining(RETRY), rejects progress with any draining error, and the inbound probe likewise rejects Draining(NOT_FOUND). The kernel preserves NOT_FOUND as the original route-invalidation cause while reporting committed retirement.
Environment and identity
eef5ad1eb1; Integration dbf5d913f8a45d685a6915f8c3d011d418e5b1dc.Evidence and prior checks
Compatibility 1.2 carries only an original directory role/selector and requested access bits. Actual sealed CLAIM clients select immutable effective credentials and original directory receipts. Vfsd checks the live metadata-directory operation and inherited namespace/write ceiling before fetching provider evidence. ReadWrite configuration cannot restore native rights. Complete canonical ACL pages preserve object/revision/count/range, order, required bases/masks and mode correspondence before any deny-only result. Partial ACLs, UID zero and combined partial group grants cannot bypass policy. Zero bits still require actual original-provider existence.
Per-query state retains one snapshot and a bounded streaming fold without a fixed ACL-entry limit. Original outbound and inbound owners remain attached through cancellation, result release and one-shot COMPLETE. Acknowledged Draining(NOT_FOUND) preserves route-loss retirement; unknown failures and unexplained absence keep custody. Stream and directory paths share the original caller helper and host fixture.
Final source review flattened the native client refusal condition without changing its requests or expected outcomes. Two additional signed cleanup/adoption commits select the final source; the implemented scope and twenty-four authored controls are unchanged. No tests, builds or CI observation were run.
Twenty-four new host controls and the extended native binding workload are authored and unrun. The native client requires seven directory-existence queries, five configured write refusals and absent-selector refusal before its inherited stream controls. Existing deadlines and resource policy are unchanged. Rustfmt was applied; all changed code remains below 1,000 lines (maximum 900) with inline rustdoc and missing_docs retained. Contracts and manual TeX are updated. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction; no pass, warning-free build or measured speedup is claimed. Generated API exports retain their explicit older source identity until generation resumes.
Native permission enforcement remains open for complete pathname/open/stat/mutation mediation and remaining provider support. Both EriX guest-build generations and rebuilding Rust/LLVM inside EriX remain required and unproved. Phase completion is 16.23% weighted, 4.81% whole-item, with 20/460 parents and 436/896 sub-items complete.
Source review of Posixd external caller release/probe against the kernel invocation caller::release, server::relinquish, teardown::status and route-invalidation lifecycle controls. Those kernel paths preserve the first NOT_FOUND cause while returning a successful native transition. Tests, builds and CI observation remain waived; no passing execution evidence is asserted.
Tracking
Fix alongside directory access, preserving native permission work and phase completion. Author controls for acknowledged NOT_FOUND, intermediate draining progress, final canonical absence, unexpected draining errors and spontaneous absence.
Related records and contracts
erikinkinen referenced this issue from erix/docs2026-09-29 13:39:15 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 13:41:48 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-29 13:42:42 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-29 13:42:44 +02:00
erikinkinen referenced this issue2026-09-29 13:42:56 +02:00
erikinkinen referenced this issue from erix/vfsd2026-09-29 13:43:13 +02:00