[BUG] Preserve provider cleanup through correlation exhaustion #8
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#8
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
Resolved: the full nonzero correlation domain is usable, and native acquisition preparation now reserves observation, acquisition and cleanup IDs before effects. Independent root/cwd cleanup retains those original correlations after exhaustion. Legacy post-effect terminal handling remains where the original cleanup route has not been independently reserved; removing that fallback would require a separate ownership conversion.
Vfsd's provider request sequence refuses the valid nonzero value
u32::MAXand invokes fail-stop on the native target when that value becomes next. The wire domain accepts every nonzero u32. This imposes an unnecessary final-value restriction and prevents ordinary owner-controlled handling of exhaustion.Reproduction
Inspect
ProviderRequestIds::allocate,can_allocateand the target-specificexhausted_provider_request_idinsrc/backend_contract.rsat revision3158ee90b5d67788d59ca71944eba671e7959cdf. Allocation computes the successor before returning the current value, and overflow invokes native fail-stop. Existing host assertions encode rejection of the maximum rather than complete-domain use.Expected and actual behavior
Expected: issue every nonzero correlation once, keep zero as a permanent exhaustion sentinel, and refuse subsequent allocations before effects without wrapping or forcibly terminating the owner. Acquisition must reserve its separate cleanup correlation before submitting a pin, so that subsequent allocation exhaustion cannot prevent its retirement.
Actual in source: the maximum is never issued; native exhaustion terminates instead of returning the checked resource-exhaustion disposition. Change the sequence and its tests, and retain pre-submission cleanup correlations in the acquisition owner. This does not claim that existing runtime cleanup failed in an observed execution.
Environment and identity
feature/posix-compat, original revision above.Evidence and prior checks
Native acquisition-scope preparation is implemented and published: lib-ipc
ab4e18f6, vfsdacc9a53a, launchd53ff53ca, posixd45976b69, exsh5308ec15, integration42f7d97b, docsfe1cd7d7.A distinct counted authority role connects public Launchd preparation, strict native scope transfer, VFS independent root/cwd ownership and sealed-client authority retirement. Root/cwd come from one actual held directory or live acquisition scope; preparation reopens no pathname and cannot widen its write ceiling. Every observation, acquisition and cleanup correlation is reserved before provider effects. Original source row, full generation, session and realm remain retained across lost replies, partial COPY and receiver disposal. Retirement disables new use before live children can delay disposal, while original child cleanup remains available. The generic broker mask and existing metadata/resize operations remain unchanged.
The native binding workload now prepares one read-only acquisition scope per client, with twenty authority rows and a 1684-byte plan per realm. Original provider and capability storage are explicitly budgeted. Twenty new controls are authored and unrun: four shared-wire, eleven VFS ownership/intake and five Launchd source/public-lifecycle cases. Existing Posixd authority, Exsh transcript and Integration geometry controls are extended. Provider correlation/cleanup and descriptor-aware source fixtures are resolved by implementation; no executed test failure or pass is claimed.
Full realm open/openat remains unfinished: native component dispatch, per-component/final permission mediation, raw path traversal, creation/append and Posixd descriptor serving still require implementation. Completion remains 16.91% weighted, 21/460 parents and 441/902 sub-items; this prerequisite adds no full-item acceptance. Tests, builds, lint checks, documentation generation, VM/profiler execution and CI observation remain deferred by instruction. Both full EriX guest-build generations and the Rust/LLVM guest rebuild remain unfinished.
Earlier evidence (historical; superseded where the current checkpoint above advances it):
Independent acquisition-root checkpoint: lib-ipc
4fefcc1f, ramfsdd9880325, e2fsdd2943a01, vfsd8c8b98d5, docs55c7e640, integrationa9c3b6b1, rootd72a63e1e.Private anchor cloning now reserves a mount-scoped original identity before submission and pins the actual held source directory without reopening a pathname. Ramfsd checks the source revision in one exclusive turn; E2fsd reserves counted handle capacity before media I/O, consumes original permission evidence and refreshes the complete live inode/ACL fingerprint. The resulting root has an independent lifetime, so source closure and a lost handle reply cannot erase its preknown cleanup identity. Mount fences prevent delayed replay, including after retirement of a key whose response was lost.
Starting anchor retirement disables ordinary root use and new component acquisition. Existing child cleanup remains available; live children return BUSY before root disposal, and final original mount/key cleanup confirms absence idempotently without media or key I/O. VFS shares its noncopyable original-route owner and state machine across component and anchor calls while preserving separate operation families and root/component versus mount/anchor identity. Both call and cleanup correlations are reserved before submission; every original echo is checked, and uncertainty retains custody.
Eighteen new controls are authored and unrun: four exact wire codecs, five Ramfsd state/dispatch cases, five ext media/dispatch cases and four VFS retained-owner cases. They cover source-independent lifetime, lost replies, cross-mount and cross-family refusal, stale evidence, replay/full-domain exhaustion, retiring-root denial and short outputs. Rustfmt was applied. Component contracts and maintained manual/API-reference source are updated. Published 56 signed commits across 55 repositories, selecting 206 Cargo and 111 catalog revisions. Rootd and both helper catalogs select the independent Rust helper
35f0b37ea8bb55f26fd52e0ae4fdee1449add810. Read-only inventory covers 3432 code files in 76 repositories, all below one thousand lines; the largest changed source is 932 lines.Full native realm open/openat remains open. Explicit native acquisition grant admission, counted source publication, VFS request dispatch, per-component/final permission mediation, creation/append effects, Posixd descriptor serving and complete native workloads remain unfinished. Original correlation/cleanup follow-up stays open until that native preparation path uses the retained owner. Existing metadata/resize grants gain no new operation authority. No new acceptance credit is added: 16.91% weighted, 21/460 parents and 441/902 sub-items. Tests, builds, lint checks, documentation generation, VM/profiler execution and CI observation remain deferred. Both EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.
Original VFS acquisition custody checkpoint: vfsd
3ac14044, docsac19ea76, integrationa31127bb.The internal acquisition owner now retains its original provider route and reserves separate call and cleanup correlations before submission. Counted noncopyable candidates bind the original VFS root row/generation, mount and provider root. All allocation families preserve their custody independently of metadata copies and native delivery clearing. Same-root directory selection, independent descendant pins and stale-selector refusal keep candidates tied to their originals. Public Close, direct record removal and private Launchd retirement refuse before provider or receiver disposal while a candidate retains the root.
Unknown or malformed responses preserve the cleanup obligation. Retirement disables ordinary use immediately and uses its original root/key and pre-reserved correlation, without another allocation or the lost handle reply. The complete nonzero provider u32 domain is issued once. Checked pre-effect acquisition reservation is separate from the legacy terminal fallback, which remains necessary when earlier effects may have occurred without independent cleanup custody. Correlation-exhaustion follow-up remains open until native acquisition grant integration and root preparation cleanup are connected.
Fourteen new transport, counted-table and actual root-close controls are authored and unrun; two counter controls are migrated. Rustfmt was applied. Component contracts and maintained manual TeX are updated. Three signed commits and three catalog selectors are published; Cargo pins and the independent Rust helper
6315e904c9d8769829928bb35108090f38c6a059remain unchanged. Read-only inventory covers 3420 code files across 76 repositories, all below one thousand lines; the largest changed source is 959 lines.This is internal ownership infrastructure. Complete realm open/openat remains open: explicit native acquisition grants, per-component and final permission mediation, VFS dispatch, creation/append effects, Posixd descriptor publication/serving and complete native workloads are unfinished. Metadata and resize endpoints acquire no new operation authority. No new acceptance credit is added; weighted completion remains 16.91%, with 21/460 parents and 441/902 sub-items accepted. Tests, builds, lint checks, documentation generation, VM/profiler execution and CI observation remain deferred. Both EriX guest-build generations and the external Rust/LLVM guest rebuild are unfinished.
The counter, maximum-value branch and native fail-stop are directly visible in the named source. Preserve non-reuse, pre-effect refusal and time/provider admission ordering. Author final-value and retained-cleanup controls; tests remain unrun under the user's deferral.
Tracking
Owning review: #3. Full acquisition: erix/posixd#17. Phase tracking: erix/integration#65.
erikinkinen referenced this issue2026-09-29 20:04:28 +02:00
erikinkinen referenced this issue from erix/docs2026-09-29 20:04:29 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 20:04:29 +02:00
erikinkinen referenced this issue from erix/blockd2026-09-29 20:37:20 +02:00
erikinkinen referenced this issue from erix/coreutils2026-09-29 20:37:31 +02:00
erikinkinen referenced this issue from erix/crashd2026-09-29 20:37:43 +02:00
erikinkinen referenced this issue from erix/deviced2026-09-29 20:37:57 +02:00
erikinkinen referenced this issue from erix/drv-acpi2026-09-29 20:38:29 +02:00
erikinkinen referenced this issue from erix/drv-i80422026-09-29 20:39:01 +02:00
erikinkinen referenced this issue from erix/drv-ps2-keyboard2026-09-29 20:39:41 +02:00
erikinkinen referenced this issue from erix/drv-ps2-mouse2026-09-29 20:39:45 +02:00
erikinkinen referenced this issue from erix/drv-rtc-cmos2026-09-29 20:39:50 +02:00
erikinkinen referenced this issue from erix/drv-serial2026-09-29 20:39:54 +02:00
erikinkinen referenced this issue from erix/drv-virtio-block2026-09-29 20:39:56 +02:00
erikinkinen referenced this issue from erix/dynlinkd2026-09-29 20:39:57 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-09-29 20:40:00 +02:00
erikinkinen referenced this issue from erix/exsh2026-09-29 20:40:02 +02:00
erikinkinen referenced this issue from erix/extop2026-09-29 20:40:04 +02:00
erikinkinen referenced this issue from erix/fatd2026-09-29 20:40:05 +02:00
erikinkinen referenced this issue from erix/fbcond2026-09-29 20:40:05 +02:00
erikinkinen referenced this issue from erix/hotplugd2026-09-29 20:40:06 +02:00
erikinkinen referenced this issue from erix/inputd2026-09-29 20:40:07 +02:00
erikinkinen referenced this issue from erix/irqd2026-09-29 20:40:09 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-29 20:40:11 +02:00
erikinkinen referenced this issue from erix/keyd2026-09-29 20:40:12 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-29 20:40:12 +02:00
erikinkinen referenced this issue from erix/lib-block2026-09-29 20:40:13 +02:00
erikinkinen referenced this issue from erix/lib-bootstrap2026-09-29 20:40:14 +02:00
erikinkinen referenced this issue from erix/lib-capabi2026-09-29 20:40:14 +02:00
erikinkinen referenced this issue from erix/lib-driver2026-09-29 20:40:15 +02:00
erikinkinen referenced this issue from erix/lib-input2026-09-29 20:40:15 +02:00
erikinkinen referenced this issue from erix/lib-interrupt2026-09-29 20:40:16 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-29 20:40:17 +02:00
erikinkinen referenced this issue from erix/lib-log2026-09-29 20:40:17 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-29 20:40:18 +02:00
erikinkinen referenced this issue from erix/lib-service2026-09-29 20:40:19 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-09-29 20:40:19 +02:00
erikinkinen referenced this issue from erix/lib-time2026-09-29 20:40:20 +02:00
erikinkinen referenced this issue from erix/lib-tty2026-09-29 20:40:20 +02:00
erikinkinen referenced this issue from erix/lib-vfs2026-09-29 20:40:21 +02:00
erikinkinen referenced this issue from erix/loaderd2026-09-29 20:40:21 +02:00
erikinkinen referenced this issue from erix/logd2026-09-29 20:40:22 +02:00
erikinkinen referenced this issue from erix/memd2026-09-29 20:40:22 +02:00
erikinkinen referenced this issue from erix/named2026-09-29 20:40:23 +02:00
erikinkinen referenced this issue from erix/pagerd2026-09-29 20:40:23 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-29 20:40:24 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-09-29 20:40:25 +02:00
erikinkinen referenced this issue from erix/probed2026-09-29 20:40:26 +02:00
erikinkinen referenced this issue from erix/procd2026-09-29 20:40:26 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-09-29 20:40:27 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-29 20:40:28 +02:00
erikinkinen referenced this issue from erix/seriald2026-09-29 20:40:29 +02:00
erikinkinen referenced this issue from erix/timed2026-09-29 20:40:30 +02:00
erikinkinen referenced this issue from erix/ttyd2026-09-29 20:40:30 +02:00
erikinkinen referenced this issue from erix/vspaced2026-09-29 20:40:32 +02:00