[FEATURE] Resolve cwd and exact operations through retained native objects #16
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#16
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
Legacy contextual cwd, launch, exact-object and redirection resolution reconstructs path spellings while providers pin directory names. This prevents required held-directory rename and detachment behavior. Independent native scopes, original candidate cleanup and actual mount-edge traversal now exist in all required providers and must become the ownership basis for these consumers.
Proposed behavior and scope
Resolve contextual paths from the actual held navigation root and current directory, keeping independent native scopes and candidates in counted Vfsd storage. Preserve exact operation/access ceilings, mount policy, raw symlink semantics and original cleanup through lost replies, cancellation, partial preparation and endpoint retirement. Treat path strings as selectors or descriptive output, never as replacements for held authority. Migrate cwd, launch, exact object/entry and redirection consumers, then remove obsolete spelling pins and provider APIs coherently. Coordinate provider and compatibility changes where required, with documentation and immutable Integration selections.
Cross-provider filesystem lifetime — signed source acceptance, 2 October 2026
Two live binding scenarios cover RAM, ext and separately selected FAT32/exFAT: conditional replacement/unlink, retained aliases and original identities, moved/detached directories, name reuse, supported links and read-only, cross-filesystem and unsupported-link refusals. Final media observers require reclaimed allocations, consistent reverse indices and clear undo ownership.
Both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Phase progress: 19.12% weighted, 7.61% whole acceptance; 27/460 parents and 485/949 sub-items.
Signed lifetime source acceptance:
Current-source acceptance now covers cwd navigation and contextual launch,
exact object/entry and redirection serving, together with compatibility shared
descriptions through namespace changes and original cleanup.
Vfsd's cwd and contextual
serving criteria are accepted; its original ownership and retired-bridge criteria
were already complete. The namespace issue also reconciles its provider criterion
with prior signed RAM/ext/FAT completion. Complete cross-provider live conditional
workloads, resource/refusal, recovery/reuse coverage and coherent runtime graph
adoption remain open. Full EriX guest generations and external Rust/LLVM rebuilding remain
required and unperformed.
Recomputed progress: 19.02% weighted, 6.81% whole acceptance; 25/460 parents and 482/949 sub-items.
Conditional relative exact-entry boundary
Add a distinct private provider acquisition family for fixed create, unlink, same-parent rename, entry metadata and touch grants. Its request names the already-held root and parent, fresh original parent revision, fixed operation, literal basename and preallocated acquisition key. It contains no mount selector, pathname or credentials. The response carries the retained entry handle, parent identity and optional original target evidence; exact-entry custody remains distinct from an ordinary content/directory candidate.
Reuse original root/key retirement for missing or malformed replies, and retain the noncopyable obligation before submission. Providers retain the original parent and target/absence independently of temporary walk handles, recheck the original ceiling and binding before later effects, and reject the entry handle on ordinary I/O, navigation or anchor creation. Native receiver cleanup remains tied to the original internal scope. Vfsd stores the fixed basename independently of descriptive path output and never reconstructs a parent by spelling. Existing exact-entry effects remain operation-bound; caller-supplied destination names cannot replace the original source binding.
Coordinate LibIPC, Vfsd, Ramfsd, E2fsd and Fatd producers/consumers. Preserve explicit format/name/capacity refusal, mount write ceilings, no-follow final entries and source-independent cleanup. Author literal codec, source retirement, moves, root crossing, absent/present target, wrong-role, reuse, lost-reply, receiver and cancellation controls. Publish immutable dependencies bottom-up; keep full migration acceptance open until path bridges, provider spelling pins and physical-report compatibility are coherently resolved.
Authority, security and reliability
Only authenticated existing directory contexts supply source custody. Retain noncopyable provider obligations before the first possible effect; copied record metadata cannot reconstruct owners. Separate internal resolution lifetimes from public scope keys and endpoints. Failed or uncertain cleanup retains disabled counted owners. Prove actual mount ancestry and provider ceilings on derivation, without acquiring a broader fallback root. Keep source, client-delivery and resulting-object cleanup independent. Priorities remain security, reliability, then performance.
Acceptance criteria
Checklist
Tests, builds, lint/format checks, generated documentation, VM/profiler execution and CI observation remain deferred by the current execution waiver. Source acceptance must not be described as executed validation. Full EriX guest builds and external Rust/LLVM rebuilding remain required.
Alternatives and tradeoffs
Keeping spelling guards preserves the old restriction. Reopening a renamed directory by a remembered path risks selecting a different object. Duplicating native mount and cleanup machinery adds conflicting ownership paths. Reuse the existing counted scope/candidate boundaries and retain only necessary active ancestry; actual storage exhaustion stays explicit. Physical path reporting may require actual ancestry observations, and cannot manufacture a path for an unreachable detached directory.
Tracking and rollout
Continue the namespace/lifetime feature, following independent FAT anchors. Linked reviews: Vfsd, Integration, manual. Track full acceptance in the phase requirements. Keep the complete migration open until every consumer and its cleanup contract is implemented.
Detailed scope and contracts
Retained-entry follow-up wire design
The conditional acquisition already fixes the original literal source name in the provider. Replace the redundant fixed-width source selector on native follow-ups with two disjoint private operations before migrating Vfsd consumers:
0x711, retained-entry mutation: a 40-byte prefix contains request/opcode (u32), original retained handle (u64), one closed mutation kind (u32: create file, create directory, unlink, remove directory, same-parent rename), destination length (u32) and canonical optional source-qualified time (16 bytes). Only rename carries a trailing raw destination basename. No source name, parent, path, root or mount selector is accepted.0x712, retained-entry touch: 56 bytes contain request/opcode, original retained handle, validated touch flags/reserved zero, explicit access and modification nanoseconds, and canonical optional source-qualified change time. The source binding is taken exclusively from the original owner.Author literal codec, malformed framing, long-name, wrong-grant/source-substitution, reply-capacity and cleanup controls. Update component/manual contracts and publish compiled immutable dependency revisions bottom-up before coherent Integration selection. This remains implementation scope within the existing five open criteria; the design does not claim completion or executed validation.
Optional descriptive path reports
Separate native object publication and identity from physical path reconstruction. A successful retained endpoint must not require a directory to have a currently enumerable pathname. Selectors remain inputs to the authenticated held root/current directory; reports never replace those owners. No missing report may be replaced by
/, the previous cwd spelling, a reconstructed provider route or a silently truncated name.Introduce a shared authority-free
VfsPathReportV1descriptor before changing the enclosing launch/cwd/report envelopes. It has a 16-byte prefix: a closed u32 kind (0unavailable,1available), four reserved zero bytes, and an exact u64 trailing byte count. Unavailable requires zero trailing bytes; available requires a nonempty absolute normalized raw path. Raw non-UTF-8 components are preserved; NUL, empty components and./..components are rejected./is a valid available root. The descriptor introduces no fixed path/name width; enclosing transport and caller storage impose their actual checked bounds. Encoding validates the whole descriptor and destination before changing any bytes.Availability describes output only. The enclosing operation must independently validate request/result correlation, original object identity and capability receipts. A failed operation has no returned owner. An unavailable report cannot convert malformed transport, lost replies, inconsistent native identity or uncertain cleanup into successful acquisition. Production report reconstruction must distinguish a definite unavailable description from failures that preserve disabled original cleanup.
Coordinate Vfsd, LibIPC, Launchd, Exsh and Coreutils where their launch, cwd or exact-report contracts change; Powerboxd already receives object identity without a pathname. Replace obsolete enclosing formats only with coordinated producers/consumers and explicit version/opcode treatment. Preserve separately authenticated command-entry/manifest binding rather than treating an optional display path as that evidence. Logical cwd availability, explicit root narrowing and absolute-selector interpretation must remain distinct from physical reporting, with no broader-root fallback.
Author literal available/unavailable, raw/long-name, malformed-kind/reserved/length, atomic short-buffer and actual custody controls. Add detached/moved-directory, source retirement, unavailable logical/physical report, launch/manifest identity, receiver and uncertain-cleanup cases while migrating consumers. Keep the broad migration criteria open until the complete publication and compatibility path uses these rules. A standalone descriptor does not establish consumer or runtime acceptance.
Exact cwd report protocol migration
Replace fixed-width exact cwd report requests/replies with V2 on new physical/logical opcodes
0x713/0x714; retire the old0x61e/0x622APIs without reusing their numbers. Requests contain request/op u32 values and an exact caller path-byte capacity u64 (16 bytes total), with no selector, handle or capability. Replies contain request/op/result u32 values and a reserved zero word, followed by one completeVfsPathReportV1. Successful unavailable output remains distinct from an operation failure. Failure carries only an unavailable descriptor. Validate correlation and the caller capacity separately from the outer receipt-free IPC header. No wire path or component maximum is introduced.Reconstruct physical descriptions into actual caller storage using retained parents and raw directory names. Only a positively observed missing name or self-parent outside the held root gives unavailable output; provider/transport/identity/cleanup failures remain errors. Retire all temporary original custody before returning either available or unavailable output. Oversized output produces a capacity failure without truncation. Preserve the logical description separately. Update Vfsd, Exsh and Coreutils together;
pwdreports unavailable without printing a substitute, and shell report refusal does not invalidate its retained cwd. Keep launch/cwd acquisition publication and manifest evidence migration open until their separate producers and consumers are converted.Author literal V2 framing/correlation/capacity controls, actual renamed/raw/long/detached cwd report controls, refusal and original cleanup controls, and consumer no-fallback cases. Tests and execution remain deferred by instruction.
Counted cwd descriptions and optional acquisition replies
Retained directory authority must outlive descriptive path availability. Replace fixed cwd description storage with immutable raw path records charged to Vfsd's existing counted invocation/handle arena. A description may occupy multiple vacant rows; it receives a nonwrapping identity and is bound to its original scope row and full generation. Reuse the already provisioned per-row byte region for descriptive chunks instead of imposing a whole-path maximum or allocating ambient memory. Description rows have no provider handle, capability or client endpoint. They reserve capacity independently of copied metadata, cannot be selected as invocation owners, and are cleared when their original scope starts retirement. Cloning into another scope creates independent storage; a copied description key cannot extend the source lifetime or select a reused row. Preflight complete capacity and framing before publishing or copying bytes.
Migrate the job-bound cwd operation to V2 on a new opcode. Keep the existing SEND-only source/staging and result receipt identities, original job/session/realm authentication and failure cleanup. Requests use full-width selector length and caller report capacity. Successful responses expose independently typed logical, physical and ceiling reports; no absent description is replaced by root, old cwd or a provider route. A failed acquisition has no result sender/object identity and only unavailable reports. Description absence cannot hide invalid native evidence or uncertain retirement.
Physical navigation starts from actual held current/root objects even when descriptive names have disappeared. Preserve the current namespace-style interpretation of absolute selectors under an explicitly narrowed root; do not reinterpret a missing root label as a broader root. Logical parent semantics, report storage and shell PWD/OLDPWD updates must be migrated coherently. Ordinary namespace-handle paths remain separate from exact-object reports. Launch command-entry/manifest binding remains independently authenticated and must not be replaced by a user selector or optional display report.
Implement counted description ownership, the V2 codec, Vfsd acquisition/report producers and Exsh receipt/environment consumers as one continuing migration. Author actual custody, source-close, detached/moved/raw/long-name, storage exhaustion/reuse, unavailable report, malformed framing, receiver and cleanup controls. Preserve the existing broad criteria until acquisition, launch consumers, provider retirement and the coherent runtime graph are all covered. Tests, builds and CI observation remain deferred by instruction.
Cwd acquisition V2 framing and optional state
Use a distinct cwd acquisition operation
0x715;0x620remains the old cwd operation until all active producers/consumers are converted, then it is retired. Logical/physical mode values remain 1/2. The V2 request is a 72-byte prefix plus the exact nonempty, NUL-free raw selector: request/op/mode/source-caller/staging/destination u32 at offsets 0/4/8/12/16/20, full selector length u64 at 24, selector digest at 32–63, and caller aggregate path-byte capacity u64 at 64. Capacity excludes reply framing and descriptor prefixes. Zero path capacity permits successful absence, but never justifies suppressing an available description. Selectors have no fixed protocol pathname width; actual transport/storage admission remains mandatory.The V2 reply has a 128-byte prefix: request/op/result/failure/mode/caller/staging/source/destination u32 at offsets 0 through 32; reserved zero u32 at 36; three u64 encoded descriptor lengths at 40/48/56; selector digest at 64–95 and original object digest at 96–127. Complete logical, physical and root-label VfsPathReportV1 descriptors follow in that order. Minimum framing is 176 bytes. Exact lengths, overflow, known status/failure classes, correlation, caller capacity and original destination must be checked. Available descriptions are normalized raw absolute bytes; no fixed path/name width is introduced. When a root label and a child description are both available, their component boundary relationship must agree. Physical mode publishes equal logical/physical descriptions, including equal absence. Logical mode preserves its separate description independently of physical reachability.
Success still requires exactly one matching SEND-only result receipt and a nonzero original object digest. Failure has zero result slots/object digest and three unavailable reports. Outer transport status and receipts are validated separately from descriptive framing; malformed evidence or uncertain cleanup cannot become successful absence. Encoding admits the complete reply before any output write and preserves unused output bytes. Vfsd must admit caller report capacity before result receiver creation or publication; a definite short buffer disposes its newly acquired candidate and leaves the caller's old cwd unchanged.
Retained root, logical and physical descriptions belong to the actual original scope generation. Eliminate native dependence on mandatory CanonicalPath fields and copied ResolverScope path metadata; ordinary namespace handle paths retain their separate contract. Root narrowing may clone an available physical label, but missing labels remain missing. Absolute selectors retain namespace-style interpretation under a known root label; missing labels must not invent root text. Relative physical traversal starts from actual held cwd/root custody even without a printable description. Logical ordinary components preserve availability; a logical parent requiring an absent spelling must fail explicitly rather than silently switch navigation semantics. Actual provider ancestry and inherited rights remain authoritative in every case.
Exsh must commit optional PWD/OLDPWD updates together with original cwd sender replacement. Available descriptions set exact bytes; absent descriptions unset the corresponding variable rather than retaining stale values or inventing root. Readonly/environment-capacity refusal occurs before committing the new sender and disposes the unpublished candidate. Snapshot/restore retains actual sender ownership; descriptive caches must not impose a fixed whole-path limit. Launch command-entry/manifest evidence remains independently authenticated and cannot be replaced by optional display bytes or caller selectors. Author framing, detached/long/raw, logical-parent, scope-generation, capacity, receipt and cleanup controls during the coordinated migration; execution remains deferred.
Resolver source identity and directory context ownership
Resolver scopes will retain only endpoint-derived source row/generation and effective namespace/write policy. Directory descriptions will be read from the original live record after authentication; copied paths or copied cwd records will no longer be part of a scope. Namespace scope construction remains explicit, distinct from a directory source. Stale/closed/reused source identities and attempted write amplification must refuse before provider work. The duplicate test-only lexical resolver will be removed in favor of the actual cwd normalizer.
Directory context installation will authenticate its counted internal scope generation, retained root and actual published candidate. Storing descriptive context does not grant cwd or enumeration rights: the original exact endpoint operation and lifetime remain unchanged and all operation/job-cwd gates remain explicit. Publication must support valid directory enumeration and invocation metadata grants. The associated source-confirmed publication regression is tracked separately.
This change is part of the remaining native-state migration. Mandatory CanonicalPath acquisition/report adapters still require removal; no detached/long cwd acceptance follows from this refactor alone.
Native optional report ownership and streamed logical traversal
Ordinary namespace handles keep their separate canonical overlay path. Native exact metadata and redirection streams must no longer require or synthesize that path. Internal scopes own optional root, logical and physical descriptions under their original generation; identical immutable reports may share a key within one scope. Cloning preserves absence and independently clones each distinct source once. Replacing report keys retires only old descriptions not retained by another report. Exported acquisition scopes need no pathname report to hold actual root/current custody.
Logical child composition and parent selection use complete raw counted descriptions. Parent rewalking streams the selected description from the actual root without a whole-path buffer. A logical parent requiring unavailable spelling/root interpretation refuses explicitly; relative physical traversal starts from the actual cwd regardless of report availability. Absolute selectors require an available original root label and a component-boundary match. Missing root labels must not become namespace root.
Description cursors support bounded original ranges and borrowed fragments, with original owner/report reauthentication after provider calls. Append composition packs unused tail space after complete capacity admission. Neither a report nor a final component gets a new static pathname limit. Reports have no provider/endpoint authority, and original retirement clears all aliases and bytes while preserving uncertain native custody.
Cwd V2 acquisition and exact queries consume these optional reports, admitting complete available byte counts before publication. Launch response and manifest identity are separate coordinated boundaries: retain their existing binding requirements until their complete producer/consumer migration, and refuse unavailable legacy evidence ordinarily with original cleanup. Never replace authenticated launch evidence with a user selector or optional display path. Controls must cover absent/long/raw descriptions, logical parents, source retirement/reuse, capacity refusal and cleanup without running them under the current testing waiver.
Held directory and resize acquisition without display-path admission
The source audit finds that Launchd never uses directory/root/resize response paths in production. These roles carry no command-entry or manifest binding requirement. Separate them from executable/sidecar resolution with receipt-only V2 directory (0x716) and resize-file (0x717) operations. The 88-byte request preserves full original transaction/session/realm, scope/destination slots, operation-specific attenuation flags, full-width selector length and digest. Raw selectors have no extra inline width; actual transport provides the bound. The exact 128-byte response preserves original correlation, result/failure, mode/size and selected-object digest, with no pathname field or fallback.
Both runtime sides must authenticate the original SEND transfer, exact destination, queried receipt and native source equality. Directory-root attenuation, resize-only purpose, job lifetime, independently retained provider owners, original-key retirement and uncertain-cleanup precedence remain unchanged. Vfsd must admit the complete response before receiver creation. Detached or unrepresentable descriptions cannot prevent relative held-directory, narrowed-root or resize acquisition. Launchd's retained descriptions must drop their unused path arrays and accessors. Retire the old directory/resize opcodes and codec acceptance after all owning consumers and authored controls migrate; no V1 downgrade retry.
Executable/sidecar resolution, authenticated command-entry identity, Loaderd graph selection and retained program display form a separate coordinated boundary. Their current binding checks remain required; this change must not replace them with caller selectors, optional display labels or unproven hashes. Continue that migration and provider/name retirement before the complete feature is accepted. Author raw/long selectors, detached source inheritance, unknown root labels, purpose/attenuation refusal, malformed/replayed receipts, retired frames and cleanup controls without executing tests or CI under the current waiver.
Digest-selected exact executable preparation
Retire the fixed-path private Loaderd preparation family after migrating Launchd and all native consumers. Add V2 operations 0x718 (ordinary executable), 0x719 (realm mediator) and 0x71A (realm client). Their 104-byte base request retains request/opcode, transaction, install destination, actual executable SEND source/staging, mode, size and original object identity. Replace pathname fields with the nonzero command-entry digest already defined as SHA-256(domain V1 || u64 little-endian raw entry length || exact authenticated entry bytes). Realm clients append the unchanged 24-byte original relation, for 128 bytes total. The 184-byte base response preserves original preparation measurements and appends that command-entry correlation; clients append the relation for 208 bytes. Refusal echoes the original entry and relation while withholding success evidence. Old operations and codecs are removed without a fallback.
Launchd derives the digest only from existing Vfsd-authenticated executable evidence, never argv[0], a caller selector or optional display labels. Loaderd compares that digest against entries of the complete runtime graph after authenticating its configured digest. Require exactly one matching executable root, then materialize the actual received executable endpoint with existing exact size, manifest and content measurement checks. The selector digest is data and cannot acquire a filesystem object, bypass runtime-graph integrity, select a service role or start a process.
Separate graph-root selection explicitly: authenticated bootstrap/service pathname selection remains on its own native lifecycle; exact executable/realm/client preparation accepts only the digest selector with actual executable SEND custody. Do not copy a graph source path into another fixed buffer, synthesize a pathname or reopen the selected executable. Preserve graph closure/cycle checks, native caller/realm relation, unique install-grant MOVE, uncertain cleanup and original rollback obligations. Both success and refusal must correlate the requested command entry before Launchd accepts returned evidence.
This completes Loaderd selection within the ongoing native launch migration. Vfsd executable/sidecar framing, counted authenticated entry evidence, retained program display, provider adapter retirement and coherent runtime adoption remain required. Author literal wire, wrong/zero digest, same-content distinct entries, long names, retired frames, native authority and cleanup controls; keep tests/builds/checks/CI deferred under the current waiver. Publish immutable dependencies bottom-up and update the manual and affected tracking records.
Counted authenticated launch-entry evidence
Replace private Vfsd launch-artifact operation 0x613 and its V1 codecs with operation 0x71B and V2 framing. The request retains the original 88-byte correlation/selector prefix and appends u64 maximum exported entry bytes at offset 88, then raw selector bytes at 96. Zero export capacity requests authenticated digest evidence without a display copy. Positive capacity requires the complete available entry, never truncation. Preserve the explicit sidecar flag, source/destination and all transaction/session/realm bindings.
The 184-byte response prefix retains request/op/result/failure at 0/4/8/12, transaction/session/realm at 16/24/32, scope/source/result slots at 40/44/48, mode at 52, size at 56, exported entry length at 64, selector digest at 72 and original object digest at 104. Add authenticated artifact-entry digest at 136, echoed export capacity at 168, echoed flags at 176 and zero reserved at 180; optional complete raw entry bytes follow at 184. Success requires a nonzero entry digest and original object evidence. Refusal preserves original request correlations while zeroing all new object, entry and measurement evidence. Both codecs reject the retired operation with no downgrade.
Vfsd derives entry identity only from complete original-generation evidence retained by the actual native resolution, never from an unchecked caller selector. Hash the existing command-entry domain, u64 little-endian complete byte length and canonical raw entry bytes in place across counted description fragments. For sidecars preserve the explicit derived .lmf requirement; the artifact hash describes the full sidecar entry, while its authenticated manifest contents remain bound to the executable command-entry digest. Missing required binding evidence refuses normally with original cleanup. Display absence cannot manufacture entry identity.
Resolve the executable selector as borrowed bytes. Derive the sidecar by streaming the original selector and literal suffix into the same counted scope traversal, without a 240-byte whole-selector buffer. Preserve known-root interpretation, actual provider authority, active symlink context, source generation and original retirement. Admit caller/transport reply extent and encode complete typed evidence before creating a receiver. Failed publication retires only new custody; uncertain cleanup stops ordinary work.
Launchd validates all original correlations, flags and capacity before accepting evidence. When entry bytes are exported, independently hash their complete bytes and require digest equality. Store the authenticated executable digest independently of its display; Loaderd and manifest binding consume that digest. Manifest evidence needs no retained path cache. Realm/client preparation requests digest-only evidence, removing the display-width obstacle on those paths. Ordinary prompted launches initially advertise their actual existing display storage capacity; continue replacing that retained storage and the coordinated Powerbox/TTY display contract in the same migration. This intermediate capacity is not full counted program-display acceptance.
Author literal wire, atomic capacity, long/raw selector, original-source closure, sidecar derivation, changed entry, retired-operation and cleanup controls. Retain existing content, relation, native receipt and rollback controls. Keep testing, builds and CI observation deferred. Complete retained display, remaining provider/name adapters and coherent deployment adoption before closing the containing native migration or claiming guest self-hosting.
Counted redirection selectors and retired provider adapters
Continue the native name migration with complete raw shell redirection selectors.
The existing request already carries a u64 length and variable tail. Remove its
unrelated legacy pathname-width check; retain exact nonempty/NUL-free bytes,
length, mode, digest and distinct slot validation. Add a public semantic validator
shared by codec and typed Vfsd admission. Vfsd must not encode a temporary fixed
pathname array merely to validate already-borrowed input. Actual caller/transport
and native traversal storage remain explicit resource bounds.
Exsh forwards original bytes and digest through its exact cwd SEND transfer and
requires independent operation/cleanup receipts. Short transport storage refuses
before any call. Vfsd authenticates the original resolver/cwd source, policy and
digest before provider effects; raw selectors do not confer authority. Existing
native scope, conditional creation, retirement and receiver-disposal ownership
remain unchanged. The wire shape and operation are unchanged; older peers may
refuse longer requests, so both compiled consumer edges adopt the signed codec.
No fallback, truncation, UTF-8 conversion or path-derived authority is permitted.
Source audit found the old ProviderBackend exact-entry open/mutate/stat/touch
hooks have no production callers. Remove their fixed-name framing, timestamped
mutation bridge, obsolete result type and operation mapper arms. Retain original-
route metadata transport used by live fixed-entry custody, and preserve current
source-free mutation/touch controls. Shared legacy provider codecs still used by
provider internals remain until their separate storage migration is complete.
Author literal raw-selector/capacity/malformed controls, direct native creation
and refusal/cleanup controls, shell full-byte transport and capacity controls,
and exact original-route metadata correlation/refusal controls. Update component
and authored manual contracts. Tests, builds, generated documents, VM/profiler
execution and CI observation remain deferred. Runtime catalog adoption and the
full cross-provider name-storage migration remain open.
Tracking: native retained ownership,
shared IPC design,
Vfsd PR3,
LibIPC PR2,
Exsh PR3,
Docs PR4.
Counted RAM namespace and retained-selection names
Replace the RAM provider's fixed basename arrays in namespace entries and retained
selection handles with private generational name keys into caller-owned records
and a separately budgeted byte arena. Names are complete raw nonempty/NUL-free
basenames. Their storage and lifetime never create native authority or replace
original parent, target, binding, root, operation or cleanup identity.
Record capacity derives from the total possible entry/handle owners plus one
serialized replacement reservation; it does not impose a separate pathname or
name-count limit. Exact byte capacity is explicit image policy, separate from file
contents. Equal complete names may share immutable storage through checked owner
counts. A copied key alone does not acquire ownership. Prepare every storage and
identity reservation before effects; publication is infallible within the same
exclusive turn. Release only the original published owner. The last owner clears
retired bytes and compacts other ranges without changing their keys. Nonwrapping
identities reject reused records; original acquisition cleanup remains available.
Migrate namespace selection, fixed entry acquisition, create, mkdir, symlink,
hardlink, rename/replacement, metadata/touch, native enumeration, consumption,
close and mount retirement together. Held-name effects take keys rather than
borrowing a mutable arena across mutation or copying another fixed buffer.
Successor namespace bindings preserve shared original names independently of
spent selection rows. Admission failures leave bytes, namespace and owner counts
unchanged. Existing native root, permission, stale-binding, directory ancestry,
read-only and one-use effect rules remain independent. Legacy fixed reply codecs
must refuse unrepresentable output explicitly, never truncate native names.
RAM capacity layout V3 uses magic ERIXRAMCAPLAY003 and 18 words: version; the five
size/alignment pairs for mount, node, entry, handle and name records; then mount
count, nodes/mount, entries/mount, file bytes/node, handles, name bytes and arena
bytes. The arena orders mount/node/entry/handle/name records, name bytes, then file
bytes. Integration policy, target geometry, CLI/shell forwarding, tracked profiles
and authored fixtures must migrate together with checked addressable arithmetic.
Retired V2 layout is rejected; no inferred production name-byte budget. Existing
compiled Rootd helper selections and runtime catalogs remain unchanged pending
coherent adoption.
Author long/raw-name native namespace and fixed-entry controls, independent
selection/entry lifetime, rename replacement, stale binding, exact byte capacity,
failed admission atomicity, last-owner clearing/compaction, mount teardown and
literal image layout controls. Update component contracts and authored manual TeX.
Tests/builds/checks/generated documents/VM/profiler execution and CI observation
remain deferred. Containing cross-provider and self-hosting acceptance stays open.
Tracking: RAM audit/design,
native ownership,
Phase 6 tracker.
Review: RAM PR2,
Integration PR12,
Docs PR4.
Counted endpoint-selected exact mutation
Replace the fixed 252-byte public VfsExactMutationRequestV1 with borrowed
VfsExactMutationRequestV2. Its 24-byte prefix contains request ID and the existing
exact operation at offsets 0/4, explicit version 2 at offset 8, reserved zero at
12 and the complete u64 destination-byte length at 16. Rename alone supplies one
raw basename after offset 24; other admitted effects have an empty tail. Empty,
NUL, slash and dot rename components refuse. Checked full extent and actual
caller/transport storage replace the fixed width and UTF-8 restriction. The
version/reserved fields distinguish valid old requests, including two-byte old
rename names, without fallback or retaining the deprecated public API.
The exact endpoint still supplies the original immutable operation and entry;
no source, parent, namespace, handle selector, new endpoint or capability is
introduced. Vfsd admits complete status capacity before provider effects and
passes the borrowed destination through the original retained owner. Existing
one-use/definite-refusal/uncertain-effect consumption and original cleanup rules
remain authoritative. Neither larger names nor descriptive status grant rights.
Migrate LibIPC, Vfsd dispatch and Coreutils source callers and controls in one
signed source graph. Coreutils uses actual encoded length and a single call;
wrong correlation, unknown status, malformed/lost replies or unexpected authority
never trigger effect replay. Retire all unwanted receipts before refusal and
preserve uncertain cleanup classification. Share the exact status-call framing,
receipt retirement and scratch clearing with existing truncation instead of
adding another transport copy. Preserve the caller's original endpoint ownership.
Author literal V2 byte layout, complete raw names, short/surplus tails, version
and reserved separation, bad shape, output canaries, operation ceilings, short
status preflight, original-provider binding/cleanup and real transport controls.
Update component contracts and maintained manual TeX. Tests/builds/checks,
generated documents, VM/profiler execution and CI observation remain deferred.
Both direct compiled IPC selectors in adopting consumers use the new immutable
revision; runtime catalogs and compiled Rootd helpers remain unchanged pending
coherent runtime adoption. Legacy directory/consumer frames and complete
cross-provider/self-hosting acceptance remain open.
Tracking: codec audit/design,
native ownership,
Coreutils audit,
Phase 6 tracker.
Review: LibIPC PR2,
Vfsd PR3,
Coreutils PR2,
Docs PR4.
Counted endpoint-selected directory enumeration
Replace the exact-endpoint use of fixed public readdir frames with dedicated
VfsExactReadDirectoryRequestV2 and VfsExactReadDirectoryResponseV2. The 32-byte
request has correlation/op at 0/4, version 2/reserved zero at 8/12, the original
endpoint-local cursor at 16 and u64 name capacity at 24. There is no public
handle, provider, candidate or namespace selector. The original ENUMERATE
endpoint remains the sole authority. Old 24-byte requests refuse on this route;
generic namespace/provider V1 contracts remain until their live users migrate.
The response has a 56-byte prefix: correlation/op at 0/4, version 2 at 8,
known result at 12, next token at 16, node kind/end flag at 24/28, observed size
at 32, complete u64 name length at 40 and reserved zero at 48. One complete raw
name follows. End and refusal have no entry, zero metadata and no name bytes;
refusal preserves the request token. A successful entry has a known kind and
a distinct nonzero token. Check the complete shape, original correlation and
offered capacity before publishing any caller-visible name or cursor.
Vfsd retains counted full native cursor state and reserves a position before
observation. Preserve native mount composition, original metadata identity and
known-size checks, original candidate retirement and equal-position reuse.
Admit complete response/name storage before publishing the reserved position;
short capacity, malformed input, provider refusal and stale identity release
the reservation without advancing the original token. Complete raw names replace
the fixed 240-byte copy. Preserve original owner retirement and generation
isolation. No path reopening, hidden fallback or name-derived authority.
Coreutils advertises the minimum of actual caller name storage and actual IPC
reply capacity, submits one call to the original endpoint, retires unexpected
receipts, validates all framing/correlation and only then copies complete names.
Erase message scratch on every return; failed admission leaves caller names
unchanged. Keep lease ownership and existing utility cursor behavior unchanged.
Use shared explicit call/disposal effects and independent reply fixtures.
Author literal codec, actual provider/position/metadata, transport cleanup and
long raw utility-listing controls. Update inline/component/manual contracts and
publish signed source with both IPC selectors in Vfsd/Coreutils coordinated.
Runtime catalogs and compiled Rootd helpers remain unchanged. Tests/builds/checks,
generated references, VM/profiler execution and CI observation remain deferred.
Complete cross-provider lifetime/restart and guest self-hosting remain open.
Tracking: codec design,
native ownership,
Coreutils audit,
Phase 6 tracker.
Retire legacy provider pathname and spelling-pin adapters
Current contextual consumers use independently retained native anchors,
conditional component/fixed-entry acquisition and source-free retained effects.
The older provider cwd-open, whole-target readlink and path-selected exact-entry
families now remain in provider dispatch, compatibility adapters and tests.
Inventory every opcode, codec and direct caller before deleting its producer.
Retire cwd component open (0x639), its whole-target link observation (0x63A), and
the obsolete path-selected fixed-entry acquisition/effect adapters where all
ordinary consumers have migrated. Old operation numbers remain unassigned and
must refuse without fallback. Keep actual native metadata, raw link pages,
conditional namespace effects, retained entry effects, original anchors and
acquisition-key retirement. Do not remove ordinary namespace/file interfaces
that still have real users, including generic provider readdir.
Remove cwd spelling-pin fields and their move/unlink guards only after the
corresponding creation paths and dependent tests migrate. Remove legacy exact
binding/parent spelling guards with their final acquisition producers. Preserve
original object, parent and navigation-ceiling ownership; empty directory moves
and detachment must retain actual held objects without pathname reopening or
reuse. Conditional entry freshness, stale-binding refusal, original one-use
effect semantics, permission evidence and positive cleanup remain mandatory.
Imported filesystem-format limits remain explicit and are not bypassed.
Migrate controls to actual native root/anchor/component/fixed-entry acquisition
with original keys known before submission. Do not emulate removed APIs with
test-only path reopeners, fabricated handles, copied identity or renamed legacy
production code. Preserve independent identity/mount separation, maximal ID and
capacity refusal, raw link lifetime, moved/detached ancestors, wrong handle kind,
stale selection/replacement, timestamps, media recovery and cleanup ordering.
Retain literal rejection controls for retired operation numbers. Share cohesive
fixture helpers where useful; all authored code stays below 1,000 lines.
Work through RAM, ext and FAT producers and dependent controls, then remove the
unused shared codecs/IDs and remaining Vfsd adapter references. Publish signed
checkpoints regularly and coordinate adopting immutable dependency revisions.
Update component contracts and authored manual/API addenda. Tests/builds/checks,
generated references, VM/profiler execution and CI observation remain deferred.
Runtime catalogs and both compiled Rootd helper selections remain unchanged
until coherent runtime adoption; full guest EriX and Rust/LLVM rebuilding remains
required. Partial provider retirement does not close the complete lifetime item.
Tracking: codec audit,
RAM audit,
ext audit,
FAT audit,
native ownership,
Phase 6 tracker.
Related records and contracts
erikinkinen referenced this issue2026-10-01 11:49:05 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 11:49:05 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 11:49:06 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-01 11:49:07 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-01 12:28:45 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-10-01 12:28:45 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-01 12:28:46 +02:00
erikinkinen referenced this issue from erix/fatd2026-10-01 12:59:08 +02:00
erikinkinen referenced this issue from erix/exsh2026-10-01 17:07:01 +02:00
erikinkinen referenced this issue from erix/coreutils2026-10-01 17:07:01 +02:00
erikinkinen referenced this issue from erix/launchd2026-10-01 19:57:32 +02:00
erikinkinen referenced this issue from erix/launchd2026-10-01 19:57:33 +02:00
erikinkinen referenced this issue from erix/loaderd2026-10-01 20:20:28 +02:00
erikinkinen referenced this issue from erix/loaderd2026-10-01 20:20:29 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-01 20:55:41 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-10-01 21:15:30 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-10-01 21:15:31 +02:00
erikinkinen referenced this issue from erix/ttyd2026-10-01 21:15:31 +02:00
erikinkinen referenced this issue from erix/ttyd2026-10-01 21:15:32 +02:00
erikinkinen referenced this issue2026-10-01 22:01:46 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 22:01:47 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 22:01:48 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-01 22:01:49 +02:00
erikinkinen referenced this issue from erix/exsh2026-10-01 22:01:50 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-10-01 22:32:23 +02:00
erikinkinen referenced this issue from erix/coreutils2026-10-01 22:56:33 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-02 00:29:07 +02:00
erikinkinen referenced this issue from erix/docs2026-10-02 00:31:00 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 00:31:51 +02:00
erikinkinen referenced this issue from erix/fatd2026-10-02 01:20:25 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-02 01:34:46 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-02 02:02:08 +02:00
erikinkinen referenced this issue from erix/blockd2026-10-02 02:34:24 +02:00
erikinkinen referenced this issue from erix/boot-tool2026-10-02 02:34:24 +02:00
erikinkinen referenced this issue from erix/bootloader2026-10-02 02:34:26 +02:00
erikinkinen referenced this issue from erix/crashd2026-10-02 02:34:27 +02:00
erikinkinen referenced this issue from erix/deviced2026-10-02 02:34:28 +02:00
erikinkinen referenced this issue from erix/drv-acpi2026-10-02 02:34:29 +02:00
erikinkinen referenced this issue from erix/drv-i80422026-10-02 02:34:30 +02:00
erikinkinen referenced this issue from erix/drv-ps2-keyboard2026-10-02 02:34:30 +02:00
erikinkinen referenced this issue from erix/drv-ps2-mouse2026-10-02 02:34:31 +02:00
erikinkinen referenced this issue from erix/drv-rtc-cmos2026-10-02 02:34:32 +02:00
erikinkinen referenced this issue from erix/drv-serial2026-10-02 02:34:33 +02:00
erikinkinen referenced this issue from erix/drv-virtio-block2026-10-02 02:34:34 +02:00
erikinkinen referenced this issue from erix/dynlinkd2026-10-02 02:34:34 +02:00
erikinkinen referenced this issue from erix/extop2026-10-02 02:34:37 +02:00
erikinkinen referenced this issue from erix/fbcond2026-10-02 02:34:39 +02:00
erikinkinen referenced this issue from erix/hotplugd2026-10-02 02:34:40 +02:00
erikinkinen referenced this issue from erix/inputd2026-10-02 02:34:41 +02:00
erikinkinen referenced this issue from erix/irqd2026-10-02 02:34:43 +02:00
erikinkinen referenced this issue from erix/kernel2026-10-02 02:34:45 +02:00
erikinkinen referenced this issue from erix/keyd2026-10-02 02:34:45 +02:00
erikinkinen referenced this issue from erix/launchd2026-10-02 02:34:46 +02:00
erikinkinen referenced this issue from erix/lib-block2026-10-02 02:34:47 +02:00
erikinkinen referenced this issue from erix/lib-bootimg2026-10-02 02:34:47 +02:00
erikinkinen referenced this issue from erix/lib-bootstrap2026-10-02 02:34:48 +02:00
erikinkinen referenced this issue from erix/lib-capabi2026-10-02 02:34:49 +02:00
erikinkinen referenced this issue from erix/lib-driver2026-10-02 02:34:50 +02:00
erikinkinen referenced this issue from erix/lib-ed255192026-10-02 02:34:50 +02:00
erikinkinen referenced this issue from erix/lib-fs-crypto2026-10-02 02:34:51 +02:00
erikinkinen referenced this issue from erix/lib-input2026-10-02 02:34:51 +02:00
erikinkinen referenced this issue from erix/lib-interrupt2026-10-02 02:34:52 +02:00
erikinkinen referenced this issue from erix/lib-log2026-10-02 02:34:53 +02:00
erikinkinen referenced this issue from erix/lib-partition2026-10-02 02:34:54 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-10-02 02:34:54 +02:00
erikinkinen referenced this issue from erix/lib-service2026-10-02 02:34:55 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-10-02 02:34:56 +02:00
erikinkinen referenced this issue from erix/lib-time2026-10-02 02:34:56 +02:00
erikinkinen referenced this issue from erix/lib-tty2026-10-02 02:34:57 +02:00
erikinkinen referenced this issue from erix/lib-vfs2026-10-02 02:34:58 +02:00
erikinkinen referenced this issue from erix/loaderd2026-10-02 02:34:59 +02:00
erikinkinen referenced this issue from erix/logd2026-10-02 02:34:59 +02:00
erikinkinen referenced this issue from erix/memd2026-10-02 02:35:00 +02:00
erikinkinen referenced this issue from erix/named2026-10-02 02:35:00 +02:00
erikinkinen referenced this issue from erix/pagerd2026-10-02 02:35:01 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-10-02 02:35:03 +02:00
erikinkinen referenced this issue from erix/probed2026-10-02 02:35:03 +02:00
erikinkinen referenced this issue from erix/procd2026-10-02 02:35:04 +02:00
erikinkinen referenced this issue from erix/rootd2026-10-02 02:35:05 +02:00
erikinkinen referenced this issue from erix/seriald2026-10-02 02:35:06 +02:00
erikinkinen referenced this issue from erix/sha2-tool2026-10-02 02:35:06 +02:00
erikinkinen referenced this issue from erix/timed2026-10-02 02:35:07 +02:00
erikinkinen referenced this issue from erix/ttyd2026-10-02 02:35:07 +02:00
erikinkinen referenced this issue from erix/vspaced2026-10-02 02:35:09 +02:00