[FEATURE] Bind conditional resizing to an explicit native file grant #6
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#6
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?
Problem and motivation
The ext and memory providers already compare retained permission revisions before truncating, but Vfsd has no exact native operation which carries that contract. Existing byte WRITE and directory READ_METADATA grants must keep their original authority rather than gain another operation family implicitly.
Proposed behavior and scope
Introduce an explicit exact-file permission-checked resize grant. It admits only the original file's permission snapshot, complete ACL pages, conditional resize and disposal. Define an exact receipt-free resize request containing original VFS object/revision correlation and the new length, without paths, private handles, credentials, clocks or replacement routes. Vfsd admits the actual original operation and write ceiling before provider observation or effects, rewrites only private handle correlation, obtains its own clock evidence and calls the existing provider conditional operation once.
This is the native effect layer of the broader compatibility permission work. Realm source preparation and Posixd's sealed-credential consumer must subsequently bind the same explicit grant before exposing a compatibility operation; they remain part of that active work. This issue does not claim a complete compatibility filesystem or guest build.
Authority, security and reliability
The original authenticated exact endpoint selects the file, provider and native operation. Record/revision numbers are descriptive correlations and cannot select another object. Existing read/write/directory grants refuse this operation family. Admission precedes request-dependent provider work; response capacity precedes effects. Metadata queries cannot consume one-shot grants. Provider comparison and mutation remain in one serialized provider turn; stale evidence refuses without automatic replay. Original native delivery retains the fixed result through failed completion, cancellation, retirement and independent receiver disposal. No capability, service discovery or private cleanup route is returned to the client.
Acceptance criteria
Checklist
Alternatives and tradeoffs
Reusing a directory metadata grant would add an unrequested mutation right. Reusing a byte-write grant for permission acquisition would silently change its operation ceiling. A separately selected resize grant keeps the compound permission/effect protocol explicit and can later be delivered through the counted realm source mechanism. Provider observations remain uncached; no performance improvement is claimed without measurement.
Tracking and rollout
Explicit native conditional resize — 29 September 2026: lib-ipc
d785e672, vfsd660d0fa1, powerboxd52a5636e, launchdba2d2a87, ttydf220da8e, docs51e49f5d, integration47fb79a7, rootd37ca91ad.The separate RESIZE_FILE grant is implemented for one retained regular file. Original byte WRITE and directory READ_METADATA operation families remain unchanged. Vfsd forwards original permission snapshots and complete ACL pages, admits the retained write ceiling, matches the public object correlation and reserves fixed result space before trusted time or provider effects. The conditional adapter uses the original private handle/revision and a fresh private request correlation. Only a correctly framed provider RETRY denotes definite staleness; uncertain transport and malformed replies become INTERNAL. There is no replay, name lookup or unconditional resize fallback.
Original native CLAIM/COMPLETE/RELINQUISH custody keeps one fixed result through completion refusal and cancellation. Metadata observations preserve one-shot custody, explicit Close covers every supported resize lifetime, and receiver-disposal failure retains the counted row. Canonical operation recognition replaces duplicated launch/broker/session lists without widening bootstrap defaults or bypassing explicit manifest, session, approval and lifetime limits. Trusted review describes permission observation and conditional resizing together.
Twenty-three new controls are authored and unrun: four wire/domain, fourteen Vfsd transport/resolver/dispatch/native-custody, two broker, one launch and two session/review controls. Component contracts and the filesystem manual are updated. Rustfmt was applied; the largest changed source has 902 lines. The read-only inventory covers 76 repositories and 3377 source files, all below one thousand lines. Fifty-five repositories are published in 56 signed commits, with 206 Cargo and 111 catalog selectors updated. Rootd's two Cargo edges and both helper catalogs retain the independent Rust-helper
5b9676ff; the later Integration catalog head stays distinct.Counted realm preparation and sealed-client conditional mediation, their native workload, other filesystem operations, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.
Related reviews: wire, Vfsd, broker, launch, session, manual, Integration. Fresh fixed-parent accounting is 16.24% weighted, 4.81% whole-item, 20/460 parents and 438/898 sub-items. The native layer receives its completed sub-item; the broader permission item remains open.
The broader consumer and producer work is tracked in erix/posixd#10 and erix/integration#65. Existing provider work: erix/e2fsd#7 and erix/e2fsd#8. Reviews: #3 and erix/lib-ipc#2. Tests, builds, lint checks, VM/manual/profiler execution and CI observation remain deferred by user instruction; preserve missing_docs and files below one thousand lines.
erikinkinen referenced this issue from erix/blockd2026-09-29 16:07:26 +02:00
erikinkinen referenced this issue from erix/coreutils2026-09-29 16:07:33 +02:00
erikinkinen referenced this issue from erix/crashd2026-09-29 16:07:45 +02:00
erikinkinen referenced this issue from erix/deviced2026-09-29 16:07:58 +02:00
erikinkinen referenced this issue from erix/docs2026-09-29 16:08:06 +02:00
erikinkinen referenced this issue from erix/drv-acpi2026-09-29 16:08:28 +02:00
erikinkinen referenced this issue from erix/drv-i80422026-09-29 16:08:45 +02:00
erikinkinen referenced this issue from erix/drv-ps2-keyboard2026-09-29 16:08:53 +02:00
erikinkinen referenced this issue from erix/drv-ps2-mouse2026-09-29 16:08:58 +02:00
erikinkinen referenced this issue from erix/drv-rtc-cmos2026-09-29 16:09:06 +02:00
erikinkinen referenced this issue from erix/drv-serial2026-09-29 16:09:13 +02:00
erikinkinen referenced this issue from erix/drv-virtio-block2026-09-29 16:09:17 +02:00
erikinkinen referenced this issue from erix/dynlinkd2026-09-29 16:09:20 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-09-29 16:09:24 +02:00
erikinkinen referenced this issue from erix/exsh2026-09-29 16:09:37 +02:00
erikinkinen referenced this issue from erix/extop2026-09-29 16:09:43 +02:00
erikinkinen referenced this issue from erix/fatd2026-09-29 16:09:44 +02:00
erikinkinen referenced this issue from erix/fbcond2026-09-29 16:09:46 +02:00
erikinkinen referenced this issue from erix/hotplugd2026-09-29 16:09:48 +02:00
erikinkinen referenced this issue from erix/inputd2026-09-29 16:09:50 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 16:09:51 +02:00
erikinkinen referenced this issue from erix/irqd2026-09-29 16:09:54 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-29 16:09:57 +02:00
erikinkinen referenced this issue from erix/keyd2026-09-29 16:09:58 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-29 16:10:00 +02:00
erikinkinen referenced this issue from erix/lib-block2026-09-29 16:10:01 +02:00
erikinkinen referenced this issue from erix/lib-bootstrap2026-09-29 16:10:02 +02:00
erikinkinen referenced this issue from erix/lib-capabi2026-09-29 16:10:03 +02:00
erikinkinen referenced this issue from erix/lib-driver2026-09-29 16:10:03 +02:00
erikinkinen referenced this issue from erix/lib-input2026-09-29 16:10:05 +02:00
erikinkinen referenced this issue from erix/lib-interrupt2026-09-29 16:10:06 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-29 16:10:07 +02:00
erikinkinen referenced this issue from erix/lib-log2026-09-29 16:10:08 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-29 16:10:09 +02:00
erikinkinen referenced this issue from erix/lib-service2026-09-29 16:10:09 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-09-29 16:10:10 +02:00
erikinkinen referenced this issue from erix/lib-time2026-09-29 16:10:10 +02:00
erikinkinen referenced this issue from erix/lib-tty2026-09-29 16:10:10 +02:00
erikinkinen referenced this issue from erix/lib-vfs2026-09-29 16:10:11 +02:00
erikinkinen referenced this issue from erix/loaderd2026-09-29 16:10:11 +02:00
erikinkinen referenced this issue from erix/logd2026-09-29 16:10:13 +02:00
erikinkinen referenced this issue from erix/memd2026-09-29 16:10:13 +02:00
erikinkinen referenced this issue from erix/named2026-09-29 16:10:14 +02:00
erikinkinen referenced this issue from erix/pagerd2026-09-29 16:10:14 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-29 16:10:15 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-09-29 16:10:16 +02:00
erikinkinen referenced this issue from erix/probed2026-09-29 16:10:48 +02:00
erikinkinen referenced this issue from erix/procd2026-09-29 16:10:49 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-09-29 16:10:49 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-29 16:10:50 +02:00
erikinkinen referenced this issue from erix/seriald2026-09-29 16:10:50 +02:00
erikinkinen referenced this issue from erix/timed2026-09-29 16:10:51 +02:00
erikinkinen referenced this issue from erix/ttyd2026-09-29 16:10:51 +02:00
erikinkinen referenced this issue2026-09-29 16:10:52 +02:00
erikinkinen referenced this issue from erix/vspaced2026-09-29 16:10:53 +02:00