[FEATURE] Declare memory effects of endpoint identity queries #57
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#57
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 frame checker discards memory facts across endpoint identity queries. The Kernel compares two caller-local slots and returns a scalar result, but its source contract does not yet describe that operation's memory effect.
Proposed behavior and scope
Declare
SAME_ENDPOINT_OBJECT(RAX=0x48) as leaving userspace memory unchanged and consume that promise through the existing live Kernel build producer. Coordinate Kernel, Exsh, Integration and the technical manual.Authority, security and reliability
Keep slot visibility, type, width and reserved-argument checks unchanged. The memory promise supplies neither a capability nor a successful identity result. Retain the conditional return ABI, original producer/source/artifact binding and complete operation origins. Unknown, mixed and pointer-bearing operations remain opaque.
Acceptance criteria
Alternatives and tradeoffs
Opaque memory remains conservative but loses useful preservation evidence. Treating all syscalls as memory-free would erase required premises. This narrow promise still needs source-backed review and does not complete the other proof obligations.
Tracking and rollout
Build on Kernel #56. Publish matching producer and consumer revisions, then select them coherently. Remaining frame work is tracked in Exsh #4 and phase completion in Integration #65.
The producer and manual are published at ca2c4735 and 5b6f22dc. Host tests cover the literal endpoint decisions and the generated ordinary/protection-key canary programs. Matching Exsh and catalog adoption, followed by the actual guest canaries, are still pending. The original frame deadline and the remaining source/route obligations stay in place.
The normal and protection-key invocation canaries pass with the published
ca2c4735Kernel and Integration84486919. They retain the original register, direction-flag and live-stack checks, guest deadlines and markers. Existing unit controls also cover wrong-type slots and reserved arguments, so the endpoint-case criterion is complete.These guests exercise the generated syscall fixture. The separate compiled-wrapper control and complete source, mapping and frame proof remain open.