[FEATURE] Demonstrate forced termination of spinning and blocked processes #62

Open
opened 2026-11-12 22:27:55 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

The Alpha 1 process-control gate must cover processes that never voluntarily yield or return from a service call.

Proposed behavior and scope

Implement the Alpha 1 scope in procd, kernel, posixd and I/O services. Follow the published Phase 6 requirements. Later-phase extensions remain separate.

Authority, security and reliability

Preserve explicit authority, original identity and resource custody across failure, cancellation and revocation. Apply security, reliability, then performance; names and observations must not create authority.

Acceptance criteria

  • An authorized controller can terminate a spinning userspace process and processes blocked in IPC or I/O.
  • Unauthorized and stale-generation requests cannot affect the process or its successor.
  • Reconcile committed effects and outstanding calls before reclaiming mappings, handles and capabilities.
  • Test termination racing timer preemption, completion, exit and revocation on 1, 2 and 4 vCPUs.

Alternatives and tradeoffs

Extend existing mechanisms where possible. Models and authored tests support the work but do not replace required original release-image evidence.

Tracking and rollout

Required by the Alpha 1 microkernel gate alongside the complete self-hosting gate. Link implementation PRs and dependencies here as they are established.

## Problem and motivation The Alpha 1 process-control gate must cover processes that never voluntarily yield or return from a service call. ## Proposed behavior and scope Implement the Alpha 1 scope in procd, kernel, posixd and I/O services. Follow the [published Phase 6 requirements](https://git.erikinkinen.fi/erix/docs/src/branch/main/phases/6.md). Later-phase extensions remain separate. ## Authority, security and reliability Preserve explicit authority, original identity and resource custody across failure, cancellation and revocation. Apply security, reliability, then performance; names and observations must not create authority. ## Acceptance criteria - [ ] An authorized controller can terminate a spinning userspace process and processes blocked in IPC or I/O. - [ ] Unauthorized and stale-generation requests cannot affect the process or its successor. - [ ] Reconcile committed effects and outstanding calls before reclaiming mappings, handles and capabilities. - [ ] Test termination racing timer preemption, completion, exit and revocation on 1, 2 and 4 vCPUs. ## Alternatives and tradeoffs Extend existing mechanisms where possible. Models and authored tests support the work but do not replace required original release-image evidence. ## Tracking and rollout Required by the [Alpha 1 microkernel gate](https://git.erikinkinen.fi/erix/integration/issues/207) alongside the [complete self-hosting gate](https://git.erikinkinen.fi/erix/integration/issues/65). Link implementation PRs and dependencies here as they are established.
erikinkinen added this to the Alpha 1 milestone 2026-11-12 22:27:55 +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/procd#62
No description provided.