[FEATURE] Own target memory while building a process #121
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/kernel#121
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
Process loaders need to create an address space, populate its memory and hand it over for execution. That construction lifetime should remain explicit across calls between the process and memory services.
Proposed behavior and scope
Introduce a native build resource created together with the target address space. It retains the target and its backing until construction finishes or aborts. Authorized build operations populate that target; execution and conflicting mapping operations remain excluded during construction.
Coordinate Kernel, LibCapabi, LibIPC and its syscall shim, Vspaced, Memd, Rootd and Procd. Process construction is the initial scope. Device/DMA ownership and live address-space editing require separate contracts.
Authority, security and reliability
Use the actual native capability and resource throughout creation, delegation, use and retirement. Keep data-frame allocator authority explicit. Identifiers and request fields describe a target; they do not grant build authority.
Specify rights attenuation, capability transfer, revocation and cleanup when a participant exits. Partial creation, allocation failure or uncertain completion must retain the existing duties and prevent premature execution. Preserve unrelated processes and their mappings.
Acceptance criteria
Alternatives and tradeoffs
Compare a dedicated build capability with extending the existing creation API. Settle transfer/copy rules and the finish-to-start transition. Favor a design that keeps policy in userspace and makes native resource lifetimes explicit.
Tracking and rollout
Part of Phase 6. Land the agreed native contract, coordinated SDK/service consumers and integration coverage as a coherent sequence. Link dependent PRs here as they become available.