Reserve a stable receiver slot for ordinary native commands #13
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/procd#13
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
Native commands need a stable child capability layout so complete inherited
descriptor tables can be placed independently of the parent's receipt storage.
The ordinary command ABI should reserve its receiver explicitly.
Proposed behavior and scope
Reserve child-local slot 4 for the bound receiver of ordinary native commands,
outside their delegated capability interval. Procd retains the actual created
receiver with the managed process and uses it when admitting startup data,
descriptions and terminal provisioning. Its local installer-grant coordinates
remain separate. Update LibCapabi, the producers, native consumers, fixtures
and technical manual together. Other service and realm creation policies keep
their own explicit layouts.
Authority, security and reliability
Use the receiver created with the original process and preserve its exact
identity, rights and generation. A numeric coordinate grants no authority.
Keep installer receipts and rollback owners attached through preparation,
start, exec and uncertain cleanup. Reject conflicting child capability
destinations before effects; descriptor numbers, lender identities and parent
source coordinates remain independent namespaces. Require coherent signed
suppliers, with no inferred receiver or compatibility fallback.
Acceptance criteria
installer-grant storage, including multiple managed rows.
wrong inventory, generation or destination refuses before effects.
while child receiver destinations are reserved independently of FD numbers.
endpoint and cleanup custody without remapping a committed transcript.
meaningful unit/integration fixtures cover the coordinated migration.
Alternatives and tradeoffs
Negotiating a receiver after preparation would require another authenticated
placement transaction. A reserved ordinary-command slot keeps the existing
intent and receipt protocols and avoids coupling child placement to parent
storage geometry.
Tracking and rollout
Implement this as a coordinated dependency of
descriptor inheritance.
Keep the phase checklist
and dependent PRs aligned with the final ABI and remaining acceptance work.