[FEATURE] Declare memory effects of endpoint identity queries #57

Open
opened 2026-10-18 19:21:23 +02:00 by erikinkinen · 2 comments
Owner

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

  • Bind the explicit promise to the selected live producer; reject missing, stale, incompatible or forged inputs.
  • Cover equal/distinct endpoints, denied/missing/wrong-type slots, zero/oversized selectors and invalid reserved arguments.
  • Preserve existing spill/cell facts only for independently established exact operations, including negative join and cross-object controls.
  • Exercise a literal protected target through the real wrapper and compare complete reports with independent controls.
  • Update documentation and the manual; complete affected checks without warnings. Keep the original 60-second gate and all route, source, mapping and frame obligations.

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.

## 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 - [ ] Bind the explicit promise to the selected live producer; reject missing, stale, incompatible or forged inputs. - [x] Cover equal/distinct endpoints, denied/missing/wrong-type slots, zero/oversized selectors and invalid reserved arguments. - [ ] Preserve existing spill/cell facts only for independently established exact operations, including negative join and cross-object controls. - [ ] Exercise a literal protected target through the real wrapper and compare complete reports with independent controls. - [ ] Update documentation and the manual; complete affected checks without warnings. Keep the original 60-second gate and all route, source, mapping and frame obligations. ## 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](https://git.erikinkinen.fi/erix/kernel/issues/56). Publish matching producer and consumer revisions, then select them coherently. Remaining frame work is tracked in [Exsh #4](https://git.erikinkinen.fi/erix/exsh/issues/4) and phase completion in [Integration #65](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

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 producer and manual are published at [ca2c4735](https://git.erikinkinen.fi/erix/kernel/commit/ca2c473520c9c97c8e1244e152cdd21e68ed7e67) and [5b6f22dc](https://git.erikinkinen.fi/erix/docs/commit/5b6f22dcf66709bb8207a958f45046d9a95b8492). 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.
Author
Owner

The normal and protection-key invocation canaries pass with the published ca2c4735 Kernel 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.

The normal and protection-key invocation canaries pass with the published ca2c4735 Kernel 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.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:30 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/kernel#57
No description provided.