[FEATURE] Preserve realm directory preparation failure context #22
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/launchd#22
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 realm filesystem VM diagnostic can report a directory-preparation refusal
as
INTERNALwithout its stored first failure class. That is insufficient todistinguish provider rejection, native progress, invalid evidence or cleanup.
Launchd has no logging route; adding one would broaden its authority.
Proposed behavior and scope
Add an explicit directory-preparation diagnostic operation on the caller's
existing Launchd endpoint. Enable it only in the existing realm-bindings
integration configuration. Preserve the ordinary 56-byte protocol exactly;
use a separate fixed 80-byte response for the diagnostic operation.
Carry the original result, typed first failure and a validated provider class
where one exists. Distinguish values already stored as u32 from retained native
i64 status; do not reconstruct information lost by older adapters.
Authority, security and reliability
Apply the ordinary caller, realm, source and generation checks before effects
and before publishing context. Report only this caller's original request;
return no paths, object IDs, slots or memory contents. Add no grant, endpoint,
logging route or command selector, and no follow-up IPC after a refusal.
Preserve the first error and independent cleanup obligations. Uncertain custody
cannot produce diagnostics or resume ordinary work. The reply is descriptive
failure data, not authority or proof that cleanup completed.
Acceptance criteria
Alternatives and tradeoffs
A new logging capability is unnecessary. Appending fields to the ordinary
reply breaks its exact framing; an additional query cannot safely recover an
uncertain request. The explicit operation keeps its lifetime and reply together.
Tracking and rollout
Supports phase completion
and remaining integration gates.
Publish coherent LibIPC, Launchd, Exsh and Integration revisions. Keep ordinary
builds and grants unchanged. This diagnostic does not establish or repair the
underlying VM refusal by itself.