Admit the original resize-file scope receipt on the private resolver #9

Closed
opened 2026-09-29 20:47:41 +02:00 by erikinkinen · 0 comments
Owner

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 VfsLaunchResolveRequestV1 with operation IPC_VFSD_OP_RESOLVE_LAUNCH_RESIZE_FILE, flags zero, an original scope SEND receipt into SLOT_VFSD_LOCAL_LAUNCHD_EXECUTABLE_STAGING_V1, and reply slot SLOT_LAUNCHD_LOCAL_WORKING_DIRECTORY_RECEIPT_V1. Pass that complete transfer frame to accept_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

  • Component: Vfsd at 8c8b98d51a829af78c6b448c75de3a070f58eba5; Integration graph at a9c3b6b17c373796a2402af397504796ba120a0e.
  • Image, hardware, firmware and toolchain: not exercised; execution is deferred by instruction.
  • Route: Launchd's private resolver with its original explicit directory scope; no generic broker or client namespace endpoint.
  • Last known working revision: unknown.

Evidence and prior checks

Private resize receipt admission is corrected: vfsd 59bce722, docs a80e255e, integration 1a9b44d3. 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.rs selects the shared filesystem result column for resize files. vfsd/src/launch_resolver_transport.rs::accept_resolve omits 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.

## 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 `VfsLaunchResolveRequestV1` with operation `IPC_VFSD_OP_RESOLVE_LAUNCH_RESIZE_FILE`, flags zero, an original scope SEND receipt into `SLOT_VFSD_LOCAL_LAUNCHD_EXECUTABLE_STAGING_V1`, and reply slot `SLOT_LAUNCHD_LOCAL_WORKING_DIRECTORY_RECEIPT_V1`. Pass that complete transfer frame to `accept_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 - Component: Vfsd at `8c8b98d51a829af78c6b448c75de3a070f58eba5`; Integration graph at `a9c3b6b17c373796a2402af397504796ba120a0e`. - Image, hardware, firmware and toolchain: not exercised; execution is deferred by instruction. - Route: Launchd's private resolver with its original explicit directory scope; no generic broker or client namespace endpoint. - Last known working revision: unknown. ## Evidence and prior checks Private resize receipt admission is corrected: [vfsd `59bce722`](https://git.erikinkinen.fi/erix/vfsd/commit/59bce722b5d66725d610c437c314a9eed8b20b46), [docs `a80e255e`](https://git.erikinkinen.fi/erix/docs/commit/a80e255e47c844ddcf2f8f072f23e30d200a9bf6), [integration `1a9b44d3`](https://git.erikinkinen.fi/erix/integration/commit/1a9b44d3d5ff3755de8e5a37c0f17974d233067d). [Vfsd issue 9](https://git.erikinkinen.fi/erix/vfsd/issues/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](https://git.erikinkinen.fi/erix/posixd/issues/17), native acquisition-scope admission, both EriX guest-build generations and external Rust/LLVM guest rebuilding remain unfinished. `launchd/src/resolver.rs` selects the shared filesystem result column for resize files. `vfsd/src/launch_resolver_transport.rs::accept_resolve` omits 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](https://git.erikinkinen.fi/erix/posixd/issues/14), [VFS native resizing](https://git.erikinkinen.fi/erix/vfsd/issues/6), [VFS implementation PR](https://git.erikinkinen.fi/erix/vfsd/pulls/3) and [Phase 6 master issue](https://git.erikinkinen.fi/erix/integration/issues/65).
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:16 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/vfsd#9
No description provided.