[BUG] Lost provider mount replies leave allocations without cleanup custody #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/vfsd#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
A lost or malformed filesystem-provider mount reply can leave an allocated provider mount without a Vfsd-owned cleanup identity. This is a source-derived reliability and resource-lifetime defect; no executed compiler, fault-injection or VM reproduction is claimed.
Reproduction
Starting from Vfsd revision
e08309b155, have a provider commit its mount allocation and suppress or corrupt the corresponding private mount response. Vfsd's mount_provider returns an error before mount_fs inserts the reserved namespace record. The provider mount ID exists only in the lost response. The old mount family supplies neither a caller-known creation key nor an original-key retirement operation. Repeat the fault to consume provider mount capacity. This is a proposed transport fault-injection sequence derived from source, not a claim that it was run.Expected and actual behavior
Expected: mount creation is counted before submission and retains a caller-known identity that can retire the original provider allocation even if no reply is received. Parent traversal custody must also remain retained until cleanup is positively complete.
Actual source behavior: the vacant namespace reservation is abandoned on the fallible mount call; no record retains a possible provider allocation and no private cleanup family can address it without the returned mount ID.
Environment and identity
e08309b155, original private provider mount family 0x620.Evidence and prior checks
Original mount creation custody and retained administrative installation are implemented and published within full Open/openat: lib-ipc
08c3a9d0, ramfsd84d60c9c, e2fsd136c1272, fatd13738d5e, vfsdc2fcb803, posixd6cbcfe53, docs962857ba, integration450c6f2a. The lost mount reply defect is fixed and closed under the testing waiver. Its reproduction remains explicitly source-derived; no executed compiler, VM or fault-injection result is claimed.Private 0x6FD creation and 0x6FE retirement carry caller-known monotonic keys, complete original correlations, canonical success/refusal shapes and known dispositions. The superseded unowned mount family and consumer adapter are removed. RAM/ext/FAT reserve original IDs and counted mount storage before initialization or media inspection/recovery. Retirement waits for dependent handles, fences stale replay and clears only the original instance. Committed ext journal recovery is not rolled back when private state retires.
Vfsd reserves the namespace record, original route and both correlations before submitting through its counted noncopyable owner. Unknown replies preserve that owner even without a returned mount ID. Administrative installation follows retained raw parent links and earlier actual mount edges, checks actual alias conflicts and covered target type, then publishes in place without losing entering-parent custody. Every failure disables installation before cleanup; refused cleanup retains its original counted row. Independent serving-loop retirement needs neither the initiating client nor fresh correlations. Existing mounts remain available while a failed pending installation drains.
FAT/exFAT supplies original mounted-root/component custody and counted retained ancestry. Retired intermediate caller records become inaccessible to ordinary operations; descendants can retain their entering edges until iterative final release. Dot-dot follows actual held parents and clamps at the original root, including exFAT. Existing identity-replacement exclusion remains effective. Fresh one-use descriptive revisions are consumed before same-turn lookup. POSIX mode/UID/GID/ACL evidence remains unknown; namespace administration does not invent compatibility access policy or acquire additional client authority. Actual compiled arena layouts include the enlarged owner records.
Twenty-one new unit controls are authored and unrun, with three existing actual mount-dispatch controls extended. They cover literal codecs, known refusal and unknown replies, original route/key/correlation cleanup after exhaustion, replay and row reuse, dependent handles, capacity before media work, actual FAT/exFAT ancestry, stale revisions, configured relative/absolute links, aliases, provider crossings, occupied namespace storage and post-creation cleanup refusal. The native realm-binding scenario installs a read-only RAM overlay through an ext symlink parent, opens it through configured and actual namespace spellings, then ascends from a live directory fd. Its explicit budget counts additional namespace and simultaneous client branch pins. No new unit control or VM workload has been executed.
Full Open remains open for conditional creation, authenticated process umask/default ACL inheritance and complete provider policy. No full Open checklist credit is added: 16.91% weighted, 5.21% whole acceptance; 21/460 parents and 441/902 sub-items. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. Tests, builds, lint checks, documentation generation, VM/profiler execution and CI observation remain deferred. No test pass, warning-free build or measured performance improvement is claimed.
Earlier evidence follows; the original mount custody and retained installation above are current.
Vfsd backend_provider/implementation.rs returns the newly allocated mount ID only after exact reply parsing; namespace.rs mount_fs inserts its vacant record only after that call succeeds. Provider dispatch commits the mount before encoding its result. These source paths establish the missing custody transition. Tests, builds and CI observation are deferred by user instruction; no execution pass or warning-free build is claimed.
Tracking
Track the original-key mount lifetime repair with full Open/openat and the Vfsd implementation PR. Add lost-reply, malformed-reply, allocation exhaustion, cleanup refusal and replay controls, and retain signed coordinated provider/consumer revisions.
erikinkinen referenced this issue from erix/blockd2026-09-30 05:58:52 +02:00
erikinkinen referenced this issue from erix/coreutils2026-09-30 05:59:01 +02:00
erikinkinen referenced this issue from erix/crashd2026-09-30 05:59:11 +02:00
erikinkinen referenced this issue from erix/deviced2026-09-30 05:59:23 +02:00
erikinkinen referenced this issue from erix/docs2026-09-30 05:59:44 +02:00
erikinkinen referenced this issue from erix/drv-acpi2026-09-30 05:59:51 +02:00
erikinkinen referenced this issue from erix/drv-i80422026-09-30 05:59:55 +02:00
erikinkinen referenced this issue from erix/drv-ps2-keyboard2026-09-30 05:59:57 +02:00
erikinkinen referenced this issue from erix/drv-ps2-mouse2026-09-30 05:59:59 +02:00
erikinkinen referenced this issue from erix/drv-rtc-cmos2026-09-30 06:00:00 +02:00
erikinkinen referenced this issue from erix/drv-serial2026-09-30 06:00:01 +02:00
erikinkinen referenced this issue from erix/drv-virtio-block2026-09-30 06:00:02 +02:00
erikinkinen referenced this issue from erix/dynlinkd2026-09-30 06:00:03 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-09-30 06:00:04 +02:00
erikinkinen referenced this issue from erix/exsh2026-09-30 06:00:06 +02:00
erikinkinen referenced this issue from erix/extop2026-09-30 06:00:07 +02:00
erikinkinen referenced this issue from erix/fatd2026-09-30 06:00:10 +02:00
erikinkinen referenced this issue from erix/fbcond2026-09-30 06:00:12 +02:00
erikinkinen referenced this issue from erix/hotplugd2026-09-30 06:00:13 +02:00
erikinkinen referenced this issue from erix/inputd2026-09-30 06:00:13 +02:00
erikinkinen referenced this issue from erix/integration2026-09-30 06:00:15 +02:00
erikinkinen referenced this issue from erix/irqd2026-09-30 06:00:16 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-30 06:00:17 +02:00
erikinkinen referenced this issue from erix/keyd2026-09-30 06:00:18 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-30 06:00:19 +02:00
erikinkinen referenced this issue from erix/lib-block2026-09-30 06:00:20 +02:00
erikinkinen referenced this issue from erix/lib-bootstrap2026-09-30 06:00:21 +02:00
erikinkinen referenced this issue from erix/lib-capabi2026-09-30 06:00:22 +02:00
erikinkinen referenced this issue from erix/lib-driver2026-09-30 06:00:23 +02:00
erikinkinen referenced this issue from erix/lib-input2026-09-30 06:00:24 +02:00
erikinkinen referenced this issue from erix/lib-interrupt2026-09-30 06:00:25 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-30 06:00:27 +02:00
erikinkinen referenced this issue from erix/lib-log2026-09-30 06:00:28 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-30 06:00:29 +02:00
erikinkinen referenced this issue from erix/lib-service2026-09-30 06:00:30 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-09-30 06:00:31 +02:00
erikinkinen referenced this issue from erix/lib-time2026-09-30 06:00:33 +02:00
erikinkinen referenced this issue from erix/lib-tty2026-09-30 06:00:34 +02:00
erikinkinen referenced this issue from erix/lib-vfs2026-09-30 06:00:35 +02:00
erikinkinen referenced this issue from erix/loaderd2026-09-30 06:00:35 +02:00
erikinkinen referenced this issue from erix/logd2026-09-30 06:00:36 +02:00
erikinkinen referenced this issue from erix/memd2026-09-30 06:00:37 +02:00
erikinkinen referenced this issue from erix/named2026-09-30 06:00:38 +02:00
erikinkinen referenced this issue from erix/pagerd2026-09-30 06:00:38 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-30 06:00:39 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-09-30 06:00:40 +02:00
erikinkinen referenced this issue from erix/probed2026-09-30 06:00:41 +02:00
erikinkinen referenced this issue from erix/procd2026-09-30 06:00:42 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-09-30 06:00:42 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-30 06:00:44 +02:00
erikinkinen referenced this issue from erix/seriald2026-09-30 06:00:45 +02:00
erikinkinen referenced this issue from erix/timed2026-09-30 06:00:45 +02:00
erikinkinen referenced this issue from erix/ttyd2026-09-30 06:00:46 +02:00
erikinkinen referenced this issue2026-09-30 06:00:47 +02:00
erikinkinen referenced this issue from erix/vspaced2026-09-30 06:00:48 +02:00