Admit the original resize-file scope receipt on the private resolver #9
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#9
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
Private resize-file preparation is rejected at VFS receipt admission even when Launchd supplies the required original scope and the correct filesystem result column. This prevents the implemented bound-file resize path from obtaining its native grant.
Reproduction
Source-derived reproduction, not an executed result: encode
VfsLaunchResolveRequestV1with operationIPC_VFSD_OP_RESOLVE_LAUNCH_RESIZE_FILE, flags zero, an original scope SEND receipt intoSLOT_VFSD_LOCAL_LAUNCHD_EXECUTABLE_STAGING_V1, and reply slotSLOT_LAUNCHD_LOCAL_WORKING_DIRECTORY_RECEIPT_V1. Pass that complete transfer frame toaccept_launch_call.The operation dispatcher recognizes resize-file resolution, but the nested reply-column match accepts only executable, manifest and directory purposes. Resize therefore falls through its rejection arm before native scope authentication or provider resolution.
Expected and actual behavior
Expected: retain the exact original scope receipt and admit the resize request for independent native scope and write-ceiling authentication. Incorrect reply slots, provenance, flags or rights must still be rejected and their received aliases disposed.
Actual by source inspection: the valid resize request is rejected and its transferred scope alias is disposed. No runtime result or CI failure has been observed.
Environment and identity
8c8b98d51a829af78c6b448c75de3a070f58eba5; Integration graph ata9c3b6b17c373796a2402af397504796ba120a0e.Evidence and prior checks
Private resize receipt admission is corrected: vfsd
59bce722, docsa80e255e, integration1a9b44d3. Vfsd issue 9 records the source-observed preparation refusal. The private dispatcher recognized resize but omitted its shared filesystem result column from receipt admission. The corrected zero-flag purpose retains Launchd's original scope SEND for native endpoint authentication and existing write-ceiling checks. Metadata, directory, byte-I/O and broker operation authority remain unchanged.Four new complete transfer-frame controls cover valid admission, artifact/arbitrary result columns, wrong provenance/rights and foreign flags. Refusal cases also cover successful and failed original-receipt disposal. Tests are authored and unrun. Rustfmt was applied; the component contract, architecture, README, roadmap and maintained manual TeX are updated. Three signed commits and three Integration catalog selections are published; Cargo pins and the independent Rust helper remain unchanged. Read-only inventory covers 3432 code files across 76 repositories, all below one thousand lines; the changed Rust file is 889 lines.
Full realm open/openat, native acquisition-scope admission, both EriX guest-build generations and external Rust/LLVM guest rebuilding remain unfinished.
launchd/src/resolver.rsselects the shared filesystem result column for resize files.vfsd/src/launch_resolver_transport.rs::accept_resolveomits resize from its reply-column selection. Existing resolver, conditional-effect and producer controls do not cover this complete transfer-frame admission boundary.Author admission controls for a valid receipt, wrong result destinations, wrong native provenance/rights and malformed flags. Test, build, lint, VM/profiler and CI execution remain deferred; no passing result is claimed.
Tracking
Related bound-file resize feature, VFS native resizing, VFS implementation PR and Phase 6 master issue.
erikinkinen referenced this issue2026-09-29 20:51:22 +02:00
erikinkinen referenced this issue from erix/docs2026-09-29 20:51:22 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 20:51:23 +02:00