[FEATURE] Bind syscall return contracts to selected Kernel builds #56
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#56
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
Exsh's native frame checker cannot carry register facts across a syscall without an explicit Kernel return contract. Matching symbols or a copied build receipt do not establish which producer supplied that contract.
Proposed behavior and scope
Declare Kernel's conditional syscall-return ABI and bind it to the selected original source, runtime feature closure, tools and freshly emitted ELF. Use the existing owned Cargo build path and pass the completed contract directly into Exsh's runtime/release frame analysis. Reuse its already built Exsh workload; prepare one bounded runtime Kernel producer before the unchanged 60-second analysis. Keep Kernel's separate minimal build and the other existing frame analyses. Coordinate Kernel, Integration and Exsh.
Authority, security and reliability
The ABI declaration is an explicit trusted semantic contract. Build correspondence does not prove compiler semantics or deployment of another image. Serialized diagnostics grant no authority. Unknown syscalls keep opaque memory effects; missing or mismatched producer inputs supply no preservation facts. Preserve existing call-target, source-membership and frame limits.
Acceptance criteria
Alternatives and tradeoffs
Discarding every register fact remains conservative but loses useful call targets. A name-based whitelist or an unbound register mask would hide the missing producer contract. The bounded build path adds correspondence checks while keeping its trust assumptions explicit.
Tracking and rollout
This supplies part of Exsh #4. Land the declaration, producer and consumer coherently, then select their exact revisions in Integration. Track phase completion in Integration #65.
The declaration is published in 32ee24c8. Integration 79ee9fbb supplies the owned producer, and Exsh fb01ad98 selects it for the existing runtime/release analysis. The actual local runtime build succeeds; the subsequent complete frame check still reaches its original 60-second deadline. This establishes build correspondence, not completed frame or guest acceptance.
Exsh 3964e913 now carries complete scalar arguments through local and native calls, retaining each original object and instruction site. The local runtime diagnostic builds the selected Kernel and records actual analyzer query transfers through the live contract; missing or mismatched producers and unknown operations retain their refusals. The producer/consumer and negative-control criteria are checked. Public manual integration and the actual CI route remain open. The complete frame check still reaches its original 60-second deadline; repeated analyzer transfers are neither unique call sites nor guest execution.
Closed on all four original contract criteria. 275fcbed supplies the technical manual. Exsh CI 600 builds the selected runtime Kernel and records actual query and unknown-operation analyzer transfers through the live consumer. That completes the CI-path criterion; its full frame analysis still reaches the original deadline and remains tracked in Exsh #4. The partial profile does not establish unique call sites or guest execution.